From: | Martijn van Oosterhout <kleptog(at)svana(dot)org> |
---|---|
To: | "Jim C(dot) Nasby" <jnasby(at)pervasive(dot)com> |
Cc: | Mischa Sandberg <mischa(at)ca(dot)sophos(dot)com>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Porting MSSQL to PGSQL (Was: [OT] MySQL is bad, but THIS bad?) |
Date: | 2006-05-22 18:45:07 |
Message-ID: | 20060522184507.GG24404@svana.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-advocacy pgsql-hackers |
On Mon, May 22, 2006 at 10:41:59AM -0500, Jim C. Nasby wrote:
> > CREATE TRIGGER name { BEFORE | AFTER } { event [ OR ... ] }
> > ON table FOR EACH STATEMENT
> > EXECUTE PROCEDURE funcname ( arguments )
>
> And that doesn't give you any information on the rows that were
> modified. Other RDBMSes will provide a NEW rowset and an OLD rowset that
> you can select from inside the trigger as if they were real tables.
Is this on the TODO list? It doesn't seem too difficult to create a
tuplestore and store the NEW and OLD tuples there and pass the whole
set to the trigger.
Have a nice day,
--
Martijn van Oosterhout <kleptog(at)svana(dot)org> http://svana.org/kleptog/
> From each according to his ability. To each according to his ability to litigate.
From | Date | Subject | |
---|---|---|---|
Next Message | Mark Woodward | 2006-05-22 18:52:29 | Re: [HACKERS] [OT] MySQL is bad, but THIS bad? |
Previous Message | Jim C. Nasby | 2006-05-22 17:20:05 | Re: [HACKERS] Toward A Positive Marketing Approach. |
From | Date | Subject | |
---|---|---|---|
Next Message | Mark Woodward | 2006-05-22 18:52:29 | Re: [HACKERS] [OT] MySQL is bad, but THIS bad? |
Previous Message | April Lorenzen | 2006-05-22 18:25:09 | error-free disabling of individual child partition tables |