From: san <san@cobalt.rmnet.it>
To: postgresql@envisity.com
To: san@cobalt.rmnet.it
Cc: pgsql-sql@postgresql.org
Subject: Re: PL/pgSQL triggers ON INSERT OR UPDATE
Date: Tue, 23 Oct 2001 21:23:00 +0200
Message-ID: <200110231923.VAA10411@cobalt.rmnet.it> (raw)
From postgresql@envisity.com Tue Oct 23 18:33:27 2001
Content-Disposition: inline
From: "Aasmund Midttun Godal" <postgresql@envisity.com>
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;
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-sql@postgresql.org
Cc: san@cobalt.rmnet.it, postgresql@envisity.com
Subject: Re: PL/pgSQL triggers ON INSERT OR UPDATE
In-Reply-To: <200110231923.VAA10411@cobalt.rmnet.it>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox