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@nooper.com - Testing - http://nooper.co.jp/labs
