Re: "No results were returned by the query" exceptions

I think next() should return false on the first call instead of an exception.
That way all the code I am used to running will work.

Maybe I am missing something in this post but from the java.sql in the
java 2 Platform:
>next
>public boolean next()
> throws SQLException
>Moves the cursor down one row from its current position. A ResultSet
>cursor is initially positioned before the first row; the first call to the
>method next makes the first row the current row; the second call makes the
>second row the current row, and so on.
>If an input stream is open for the current row, a call to the method next
>will implicitly close it. A ResultSet object's warning chain is cleared
>when a new row is read.
>Returns:
>true if the new current row is valid; false if there are no more rows
>Throws:
>SQLException - if a database access error occurs

Note: false if there are no more rows. I would think this would apply to an
empty
result set and return false on the first call - not throw an exception. I
think,
if I am not mistaken, this what other DB's do. Is the original poster
correct about
an exception? Maybe there was a real database access error as well.

At 09:47 AM 3/20/2002 +0900, Thomas O'Dowd wrote:
>Hi Tim,
>
>I'm not using the latest driver right now, but I can't see why it
>should do this because a) the driver doesn't currently support
>error codes so without parsing the error message you can't tell
>if its a real error or not. b) isn't this what ResultSet.next() is
>for? c) in my understanding of the java api, that would be unexpected
>behaviour. I maybe wrong but I'd love to hear the reasons why.
>
>Tom.
>
>On Wed, Mar 20, 2002 at 11:00:52AM +1100, Tim Lewis wrote:
> > Hi people,
> >
> > Am I correct in assuming that the new driver now throws an exception
> > when a "No results were returned by the query" occurs for a prepared sql
> > statement. I have recently upgraded the driver from 7.1 to 7.2 and my
> > application now throws this exception when a query returns no rows in
> > the result set.
> >
> > Could someone clarify this with me.
> >
> > Thanks,
> >
> > Tim Lewis
> >
> >
> > ---------------------------(end of broadcast)---------------------------
> > TIP 6: Have you searched our list archives?
> >
> > http://archives.postgresql.org
>
>--
>Thomas O'Dowd. - Nooping - http://nooper.com
>tom(at)nooper(dot)com - Testing - http://nooper.co.jp/labs
>
>---------------------------(end of broadcast)---------------------------
>TIP 5: Have you checked our extensive FAQ?
>
>http://www.postgresql.org/users-lounge/docs/faq.html