Re: Stamping rows... - Mailing list pgsql-admin

From Michael Fuhr
Subject Re: Stamping rows...
Date
Msg-id 20041122015612.GA42649@winnie.fuhr.org
Whole thread Raw
In response to Stamping rows...  ("Di Croce, Tony" <tdicroce@pelco.com>)
List pgsql-admin
On Thu, Nov 18, 2004 at 04:23:50PM -0800, Di Croce, Tony wrote:
> I am trying to find a way to stamp all of the rows affected by an update (or
> insert) with a unique value.

[snip]

> At first I tried to do this as a trigger function. The problem with this
> solution is that if I dont have the function called for each row, I cannot
> modify those rows. if I DO have the function called for each row, how do
> they get the "change_number" they cannot simply call nextval() as it will be
> different for each row (they also couldn't call curval() because then who is
> ever calling nextval()?)

Have you tried calling nextval() in a FOR EACH STATEMENT trigger
and currval() in a FOR EACH ROW trigger?  This works for me in
simple tests.  I don't know if statement triggers are guaranteed
to fire before row triggers, but they do appear to work that way.

--
Michael Fuhr
http://www.fuhr.org/~mfuhr/

pgsql-admin by date:

Previous
From: Nicholas Walker
Date:
Subject: Escape Quoting
Next
From: "Chris Hoover"
Date:
Subject: URGENT - HELP WITH 7.3.4 Strangeness