The actual trigger function I'm working with is over two screens long and
rather expensive to be calling twice! Perhaps I need to add another trigger
that updates the log table with the correct values after the fact. Recursive
triggers, fun! Thanks for the help,
Ang Chin Han wrote:
> Either somehow rewrite your trigger as a rule, or stick another
> trigger to change the value before getting into your log table.
> You might be able to reuse your trigger function, I think, just
> point the trigger to that function. A bit inefficient, since it
> gets called twice.
In response to
pgsql-sql by date
|Next:||From: Mailing List Expander||Date: 2000-08-11 02:46:21|
|Subject: Problem with SQL query (eats swap)|
|Previous:||From: Ang Chin Han||Date: 2000-08-10 02:18:20|
|Subject: Re: Rules aren't doing what I expect|