Re: [HACKERS] Proposal for db level triggers

2008-05-07 Thread Bruce Momjian
Added to TODO: * Add database and transaction-level triggers http://archives.postgresql.org/pgsql-hackers/2008-03/msg00451.php --- Decibel! wrote: > > On Mar 13, 2008, at 5:14 PM, James Mansion wrote: > > > James Mans

Re: [HACKERS] Proposal for db level triggers

2008-03-21 Thread alfranio
Hi, We have something that seems to work and may be used as a start point. Please, take a look at http://gorda.di.uminho.pt/community/pgsqlg/ In particular, take a look at the file src/backend/commands/triggerspecial. Cheers, Alfranio. > > On Mar 13, 2008, at 5:14 PM, James Mansion wrote: > >

Re: [HACKERS] Proposal for db level triggers

2008-03-20 Thread Decibel!
On Mar 13, 2008, at 5:14 PM, James Mansion wrote: James Mansion wrote: In usage: AFTER START clears counters and flags. UPDATE triggers on data set counters and flags. BEFORE COMMIT examines the counters and flags and performs any final validation or adjustments (or external events such as

Re: [HACKERS] Proposal for db level triggers

2008-03-14 Thread Pavan Deolasee
On Fri, Mar 14, 2008 at 3:44 AM, James Mansion <[EMAIL PROTECTED]> wrote: > > And if we use data update triggers to insert into a DELETE ROWS temp > table or an in-memory data > structure, the BEFORE COMMIT trigger is the place to do a bulk copy into > real table(s) or combine > rows into a B

Re: [HACKERS] Proposal for db level triggers

2008-03-13 Thread James Mansion
James Mansion wrote: In usage: AFTER START clears counters and flags. UPDATE triggers on data set counters and flags. BEFORE COMMIT examines the counters and flags and performs any final validation or adjustments (or external events such as sending a MoM message) I'd like to point out also th

[HACKERS] Proposal for db level triggers

2008-03-12 Thread James Mansion
Background: Firebird 2.1 allows: CREATE TRIGGER name ON ( CONNECT | DISCONNECT | TRANSACTION START | TRANSACTION COMMIT | TRANSACTION ROLLBACK ) I want to allow syntax: CREATE TRIGGER event event (3 variations, application can specify any number of them): AFTER CONNECT AFTER TRANSACTION