| From: | "Scott Marlowe" <scott(dot)marlowe(at)gmail(dot)com> |
|---|---|
| To: | "Dale Harris" <itsupport(at)jonkers(dot)com(dot)au> |
| Cc: | "Klint Gore" <kgore4(at)une(dot)edu(dot)au>, "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: can't get UPDATE ... RETURNING ... INTO ... to compile successfully |
| Date: | 2008-08-20 05:02:56 |
| Message-ID: | dcc563d10808192202xc063d9bgf58d6e859b1b669d@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Tue, Aug 19, 2008 at 9:51 PM, Dale Harris <itsupport(at)jonkers(dot)com(dot)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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Scott Marlowe | 2008-08-20 05:06:55 | Re: schema name in SQL statement. |
| Previous Message | johnf | 2008-08-20 04:53:11 | Re: schema name in SQL statement. |