From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
---|---|
To: | Martijn van Oosterhout <kleptog(at)svana(dot)org> |
Cc: | "Jim C(dot) Nasby" <jnasby(at)pervasive(dot)com>, 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 19:14:18 |
Message-ID: | 20060522191418.GA13518@surnet.cl |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-advocacy pgsql-hackers |
Martijn van Oosterhout wrote:
> 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.
OTOH it would be nice to be able to save only the TIDs of the tuples,
not the tuples themselves ... maybe create a "TIDstore"?
--
Alvaro Herrera http://www.CommandPrompt.com/
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
From | Date | Subject | |
---|---|---|---|
Next Message | Martijn van Oosterhout | 2006-05-22 19:14:30 | Re: [HACKERS] [OT] MySQL is bad, but THIS bad? |
Previous Message | Bruce Momjian | 2006-05-22 19:11:14 | Re: Porting MSSQL to PGSQL (Was: [OT] MySQL is bad, but THIS |
From | Date | Subject | |
---|---|---|---|
Next Message | Martijn van Oosterhout | 2006-05-22 19:14:30 | Re: [HACKERS] [OT] MySQL is bad, but THIS bad? |
Previous Message | Bruce Momjian | 2006-05-22 19:11:14 | Re: Porting MSSQL to PGSQL (Was: [OT] MySQL is bad, but THIS |