On Mon, May 22, 2006 at 03:11:14PM -0400, Bruce Momjian wrote: > Martijn van Oosterhout wrote: > -- Start of PGP signed section. > > 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. > > TODO has: > > * Allow statement-level triggers to access modified rows
No wonder I missed it, it's under the RI section. :) Actually, it looks like there's a bunch of things in there that are generic trigger issues and not really RI issues. And some of those are exact duplicates of the triggers section... wee! -- Jim C. Nasby, Sr. Engineering Consultant [EMAIL PROTECTED] Pervasive Software http://pervasive.com work: 512-231-6117 vcard: http://jim.nasby.net/pervasive.vcf cell: 512-569-9461 ---------------------------(end of broadcast)--------------------------- TIP 4: Have you searched our list archives? http://archives.postgresql.org