From: | Dale <harris_da(at)yahoo(dot)com(dot)au> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: can't get UPDATE ... RETURNING ... INTO ... to compile successfully |
Date: | 2008-08-18 22:34:48 |
Message-ID: | c7f4707c-56a8-4923-8bbb-78a5e547b315@x16g2000prn.googlegroups.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Aug 18, 9:23 pm, Lew <no(dot)(dot)(dot)(at)lewscanon(dot)com> 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.
>
> > UPDATE "EntityRelation" SET "Status" = inStatus, "Modified" =
> > Session_TimeStamp(), "ModifiedBy" = UserID() WHERE ("RelationID" =
> > inRelationID) AND ("EntityID" = inEnityID) AND IsEqual(inRelatedID,
> > "RelatedID") RETURNING "Default" INTO oldDefault;
>
> > Does anyone have any ideas if the INTO clause actually works at all
> > for an UPDATE statement?
>
> <http://www.postgresql.org/docs/8.3/static/sql-update.html>
> does not list an INTO clause for UPDATE, and when you think about it, indeed
> such a clause doesn't make sense.
>
> --
> Lew
http://www.postgresql.org/docs/8.3/static/plpgsql-statements.html
As per this documentation, you should be able to do it. It works for
the INSERT command, but not UPDATE. For the INSERT command, it makes
my code look neater and I image it's more efficient too.
Dale.
From | Date | Subject | |
---|---|---|---|
Next Message | Ow Mun Heng | 2008-08-19 00:43:45 | Re: What's size of your PostgreSQL Database? |
Previous Message | Dmitry Koterov | 2008-08-18 20:36:30 | Re: Changing between ORDER BY DESC and ORDER BY ASC |