"Gauthier, Dave" writes:
> Ya, I worded the original poorley. Let me try again
> The after update trigger on the table sets some of the NEW.column values for
> record A. Then it executes another update on the same table, but on record
> B. That second execution of the update trigger needs
From: Craig Ringer [mailto:cr...@postnewspapers.com.au]
Sent: Sunday, January 24, 2010 11:34 AM
To: Gauthier, Dave
Cc: pgsql-general@postgresql.org
Subject: Re: [GENERAL] Recursion in triggers?
Gauthier, Dave wrote:
> What I need to know is if, in the "after" update trigger I make the
&g
Gauthier, Dave wrote:
> What I need to know is if, in the “after” update trigger I make the
> subsequent updates to other records in the same table, with the OLD/NEW
> record ponters be set properly in those subsequent update trigger
> invocations?
They'll be set properly. I'm not sure they'll be
On 24 Jan 2010, at 5:36, Gauthier, Dave wrote:
> Hi:
>
> I’m dealing with a hierarchical design where changes in one record can and
> should cause changes in other records lower inthe hierarchy. I’m trying to
> use update triggers to do this. And recursion would be a real nice way to
> do
Hi:
I'm dealing with a hierarchical design where changes in one record can and
should cause changes in other records lower inthe hierarchy. I'm trying to use
update triggers to do this. And recursion would be a real nice way to do this.
What I need to know is if, in the "after" update trigge
