Re: getUdateCount() vs. RETURNING clause - Mailing list pgsql-jdbc

From Thomas Kellerer
Subject Re: getUdateCount() vs. RETURNING clause
Date
Msg-id hej80d$h7p$1@ger.gmane.org
Whole thread Raw
In response to Re: getUdateCount() vs. RETURNING clause  (Oliver Jowett <oliver@opencloud.com>)
Responses Re: getUdateCount() vs. RETURNING clause
List pgsql-jdbc
Oliver Jowett, 25.11.2009 13:16:
>> So if I create a loop using the condition stated in the Javadocs the
>> program flow would be as follows:
>>
>> 1) stmt.execute() returns true, so I call getResultSet()
>> 2) getMoreResults() returns false, but getUpdateCount() returns 3 ==> go on
>> 3) getMoreResults() returns false, but getUpdateCount() returns 2 ==> go on
>> 4) getMoreResults() returns true, so getResultSet() returns a result set
>> ==> go on
>> 5) getMoreResults() returns true, so getResultSet() returns a result set
>> ==> go on
>> 6) getMoreResults() returns false, getUpdateCount() returns -1 ==>
>> everything was processed.
>
> Yes, this is correct. It will look something like this:

So my understanding was correct ;)

Back to my original question then: why doesn't the Postgres driver return 1 as the updateCount in this situation?

I only get a single result set (which is correct) but never a 1 as the update count.

Regards
Thomas

pgsql-jdbc by date:

Previous
From: Oliver Jowett
Date:
Subject: Re: getUdateCount() vs. RETURNING clause
Next
From: Oliver Jowett
Date:
Subject: Re: getUdateCount() vs. RETURNING clause