Received: from cobalt.rmnet.it (cobalt.rmnet.it [194.183.26.12]) by postgresql.org (8.11.3/8.11.4) with ESMTP id f9NJNPP78543 for ; Tue, 23 Oct 2001 15:23:25 -0400 (EDT) (envelope-from san@cobalt.rmnet.it) Received: (from san@localhost) by cobalt.rmnet.it (8.9.3/8.9.3) id VAA10411; Tue, 23 Oct 2001 21:23:00 +0200 Date: Tue, 23 Oct 2001 21:23:00 +0200 From: san Message-Id: <200110231923.VAA10411@cobalt.rmnet.it> To: postgresql@envisity.com, san@cobalt.rmnet.it Subject: Re: PL/pgSQL triggers ON INSERT OR UPDATE Cc: pgsql-sql@postgresql.org X-Archive-Number: 200110/341 X-Sequence-Number: 5294 From postgresql@envisity.com Tue Oct 23 18:33:27 2001 Content-Disposition: inline From: "Aasmund Midttun Godal" To: san@cobalt.rmnet.it Cc: pgsql-sql@postgresql.org Subject: Re: [SQL] PL/pgSQL triggers ON INSERT OR UPDATE Date: Tue, 23 Oct 2001 16:31:12 GMT X-Mailer: Googley-Moogley First, I may be wrong but I do think they would prefer if you did not cross-post (especially to hackers). Second I think it probably make more sense to make two different triggers here. If you really wanted to do it that way you might want to try executing that part. Regards, Aasmund. Thank you, I should have been *really* tired that night, but it is working now ... No more complaints about missing OLD variable. It works as I wanted. One trigger for both events, checks for TG_OP. Sorry about cross-posting attempt ;) please don't post that mail --san;