Re: Problem with move not returning number of rows affected [was: error when using move, any suggestions?]

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Barry Lind <blind(at)xythos(dot)com>
Cc: Noel <noel(dot)faux(at)med(dot)monash(dot)edu(dot)au>, "pgsql-jdbc(at)postgresql(dot)org" <pgsql-jdbc(at)postgresql(dot)org>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Problem with move not returning number of rows affected [was: error when using move, any suggestions?]
Date: 2002-12-26 18:31:50
Message-ID: 2195.1040927510@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-jdbc

Barry Lind <blind(at)xythos(dot)com> writes:
> The code is expecting the server to return the keyword MOVE followed by
> the number of rows actually moved. And on all tests on my databases
> this is always true, move is followed by a number. However from the
> information you have provided, it seems that on your database the server
> is just returning MOVE without the row count. At first pass this
> appears to be a bug in the server.

No, a version discrepancy. MOVE didn't return a row count before 7.2.

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2002-12-26 18:41:52 Re: MOVE strangeness
Previous Message Tom Lane 2002-12-26 18:26:11 Re: MOVE strangeness

Browse pgsql-jdbc by date

  From Date Subject
Next Message Barry Lind 2002-12-26 18:52:02 Re: Accessing BIT(n) type from Java
Previous Message Felipe Schnack 2002-12-26 18:00:40 Re: statement's hashCode()