db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Kathey Marsden <kmarsdende...@sbcglobal.net>
Subject Re: EG meeting feedback - July 27, 2005
Date Mon, 08 Aug 2005 14:54:35 GMT

> In particular there are two things I wish to address:
>
> 1) ResultSet.next() after last row of FORWARD_ONLY cursor throws an
> SQL Exception with Network Server
>
> I started working on this issue approximately 2 months ago and while
> it has brought about a great deal of discussion there have been no
> changes in the code to bring about a resolution to this issue. As I
> allude to in my summary of the meeting with the Expert Group it would
> seem that the most common approach taken by other JDBC vendors is to
> return false after the last Row of the ResultSet for a FORWARD_ONLY
> cursor. The exact state of the ResultSet when this value is returned
> may differ from vendor to vendor but the output is the same. I
> propose, at least for the moment, the Client be changed to match
> Embedded in this regard. In this way we succeed in bringing the two
> drivers more in line with one another and if we later find that this
> is not the correct approach then both client and Embedded can be changed. 


I agree,  I think since we voted to have client match embedded and, the
different vendors behave differently on this issue,  and the EG could
provide no clear definition of the correct behavior, it makes sense  go
ahead and match embedded for  this case.




Mime
View raw message