On Wed, Aug 20, 2008 at 11:25 PM, Dale <[EMAIL PROTECTED]> wrote:
> This afternoon I'm
> starting to notice that pgAdmin III for Windows sometimes gives
> erratic error messages when there is no error or the error is actually
> different. I know this because when I recompile after moving the
> cu
Alvaro Herrera <[EMAIL PROTECTED]> 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 th
In response to Alvaro Herrera <[EMAIL PROTECTED]>:
> 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?
Because a doc linked to earlier in this threa
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?
alvherre=> create table bill (a int, b text);
CREATE TABLE
alvherre=> insert into bill values (1, 'one');
INSER
In response to Dale <[EMAIL PROTECTED]>:
> On Aug 18, 9:23 pm, Lew <[EMAIL PROTECTED]> wrote:
> > Dale wrote:
> > > Hi,
> > > I've got some code which postgres 8.3.3 won't accept. Postgres
> > > doesn't like the INTO clause on RETURNING INTO and I've tried
> > > following the documentation.
> >
>
