Received: from nts1.rtp.epa.gov (nts1.rtp.epa.gov [134.67.208.208]) by hub.org (8.10.1/8.10.1) with ESMTP id e7AENYG42597 for ; Thu, 10 Aug 2000 10:23:34 -0400 (EDT) Received: from epamail.epa.gov (IDENT:mvs@wolfpack.rtpnc.epa.gov [134.67.139.59]) by nts1.rtp.epa.gov (8.9.3/8.9.3) with ESMTP id KAA09785; Thu, 10 Aug 2000 10:26:43 -0400 (EDT) Message-ID: <3992BAB7.AE1D4FC3@epamail.epa.gov> Date: Thu, 10 Aug 2000 10:22:47 -0400 From: Mark Volpe X-Mailer: Mozilla 4.74 [en] (X11; U; Linux 2.2.14-15mdk i586) X-Accept-Language: en MIME-Version: 1.0 To: Ang Chin Han CC: pgsql-sql@postgresql.org Subject: Re: Rules aren't doing what I expect References: <399180FD.2ACF8B2D@epamail.epa.gov> <20000810101820.A8537@pintoo.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Archive-Number: 200008/72 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, Mark 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.