Tom Lane wrote:
> Achilleus Mantzios <achill(at)matrix(dot)gatewaynet(dot)com> writes:
> > Is there a reason that the NEW values should remain unchanged in AFTER
> > row triggers?
> By definition, an AFTER trigger is too late to change what was stored.
> Use a BEFORE trigger.
But a BEFORE trigger would alter the stored tuple, which is not what
Achilleus wants AFAIU.
I think the desired effect can be had by having DBMirror check the
source relation of the inserted tuple (There is a hidden attributa
called tableoid IIRC that can be used for that, I think).
Alvaro Herrera http://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc.
In response to
pgsql-sql by date
|Next:||From: Tom Lane||Date: 2006-02-24 17:37:51|
|Subject: Re: After Trigger assignment to NEW |
|Previous:||From: Achilleus Mantzios||Date: 2006-02-24 16:44:08|
|Subject: After Trigger assignment to NEW|