Re: Re: can't get UPDATE ... RETURNING ... INTO ... to compile successfully - Mailing list pgsql-general

From Tom Lane
Subject Re: Re: can't get UPDATE ... RETURNING ... INTO ... to compile successfully
Date
Msg-id 21834.1219159791@sss.pgh.pa.us
Whole thread Raw
In response to Re: Re: can't get UPDATE ... RETURNING ... INTO ... to compile successfully  (Alvaro Herrera <alvherre@commandprompt.com>)
Responses Re: can't get UPDATE ... RETURNING ... INTO ... to compile successfully  ("Dale Harris" <itsupport@jonkers.com.au>)
List pgsql-general
Alvaro Herrera <alvherre@commandprompt.com> writes:
> Bill Moran wrote:
>> Is it possible that your UPDATE command is updating multiple rows?  I
>> don't believe RETURNING will work on an UPDATE that touches more than 1
>> row.

> Hmm, why not?

plpgsql will reject UPDATE RETURNING INTO that returns more than one
row, since it hasn't got any place to put the additional data.

It wasn't clear to me whether the OP was even using plpgsql, but if he
was, the example should have worked.  We'd need to see more detail to
guess what the real problem is.

            regards, tom lane

pgsql-general by date:

Previous
From: Tom Lane
Date:
Subject: Re: Idle in transcation problem?
Next
From: Goboxe
Date:
Subject: Re: PostgreSQL on Windows x64