From: | san <san(at)cobalt(dot)rmnet(dot)it> |
---|---|
To: | postgresql(at)envisity(dot)com, san(at)cobalt(dot)rmnet(dot)it |
Cc: | pgsql-sql(at)postgresql(dot)org |
Subject: | Re: PL/pgSQL triggers ON INSERT OR UPDATE |
Date: | 2001-10-23 19:23:00 |
Message-ID: | 200110231923.VAA10411@cobalt.rmnet.it |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-sql |
From postgresql(at)envisity(dot)com Tue Oct 23 18:33:27 2001
Content-Disposition: inline
From: "Aasmund Midttun Godal" <postgresql(at)envisity(dot)com>
To: san(at)cobalt(dot)rmnet(dot)it
Cc: pgsql-sql(at)postgresql(dot)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;
From | Date | Subject | |
---|---|---|---|
Next Message | Andre Schnabel | 2001-10-23 20:17:59 | Re: Diferent databases on same query... |
Previous Message | Tom Lane | 2001-10-23 19:14:14 | Re: Index of a table is not used (in any case) |