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

From Scott Marlowe
Subject Re: can't get UPDATE ... RETURNING ... INTO ... to compile successfully
Date
Msg-id dcc563d10808192202xc063d9bgf58d6e859b1b669d@mail.gmail.com
Whole thread Raw
In response to Re: can't get UPDATE ... RETURNING ... INTO ... to compile successfully  ("Dale Harris" <itsupport@jonkers.com.au>)
List pgsql-general
On Tue, Aug 19, 2008 at 9:51 PM, Dale Harris <itsupport@jonkers.com.au> wrote:
> As per the original message:

>>UPDATE "EntityRelation" SET "Status" = inStatus, "Modified" =
>> Session_TimeStamp(), "ModifiedBy" = UserID() WHERE ("RelationID" =
>> inRelationID) AND ("EntityID" = inEnityID) AND IsEqual(inRelatedID,
>> "RelatedID") RETURNING "Default" INTO oldDefault;

This is called a code fragment.  What people want to see here is a
self-contained example of it failing.  Until you post one of those, no
one can troubleshoot it because it WORKS FOR THEM.

Create a test table
insert some data
create a plpgsql function
call that function and have it throw an error.

Post all of that here.

pgsql-general by date:

Previous
From: johnf
Date:
Subject: Re: schema name in SQL statement.
Next
From: "Scott Marlowe"
Date:
Subject: Re: schema name in SQL statement.