Skip site navigation (1) Skip section navigation (2)

Re: Stored Procedure Record Updates using For Loops - Postgres 8.1

From: "Lummis, Patrick J" <PJL(at)dolby(dot)com>
To: "Adrian Klaver" <adrian(dot)klaver(at)gmail(dot)com>, <pgsql-general(at)postgresql(dot)org>
Cc: "Bartosz Dmytrak" <bdmytrak(at)eranet(dot)pl>
Subject: Re: Stored Procedure Record Updates using For Loops - Postgres 8.1
Date: 2012-02-28 22:06:17
Message-ID: 05BB196AB3DA6C4BBE11AB6C957581FE438CA468@sfo-exch-01.dolby.net (view raw or flat)
Thread:
Lists: pgsql-general
Indeed there is an id field. That's the ticket!

And thanks much. 

-----Original Message-----
From: Adrian Klaver [mailto:adrian(dot)klaver(at)gmail(dot)com] 
Sent: Tuesday, February 28, 2012 12:48 PM
To: pgsql-general(at)postgresql(dot)org
Cc: Lummis, Patrick J; Bartosz Dmytrak
Subject: Re: [GENERAL] Stored Procedure Record Updates using For Loops -
Postgres 8.1

On Tuesday, February 28, 2012 12:35:58 pm Lummis, Patrick J wrote:
> Hi Bartek,
> 
> Thanks for the quick response.
> 
> Syntax error cleared up and loads fine but executing the stored 
> procedure fails to update the row.

From the usage I guessing this function is not being used in a trigger.
As such the ROW variable exists outside the table. If you want to UPDATE
the table you are going to have to do a hybrid of what you have:

update workorder set wfstatus='failed' where id=workorderRecord.id

assuming there is an 'id' field of some sort.


> 
> Regards,
> 
> Patrick

--
Adrian Klaver
adrian(dot)klaver(at)gmail(dot)com

In response to

pgsql-general by date

Next:From: Andy ColsonDate: 2012-02-28 22:21:32
Subject: Re: strategies for dealing with frequently updated tables
Previous:From: dennis jenkinsDate: 2012-02-28 22:01:23
Subject: Re: accumulating handles problem on machine running postgresql

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group