Re: Proposal for db level triggers - Mailing list pgsql-hackers

From alfranio@lsd.di.uminho.pt
Subject Re: Proposal for db level triggers
Date
Msg-id 40937.192.168.82.158.1206129524.squirrel@webmail.lsd.di.uminho.pt
Whole thread Raw
In response to Re: Proposal for db level triggers  (Decibel! <decibel@decibel.org>)
List pgsql-hackers
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:
>
>> 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 that AFTER CONNECT is a good opportunity
>> to CREATE TEMP TABLE (be
>> nice if a global temp table definition could be persisted and
>> automatically duplicated into each session, but
>> never mind).
>
> +1 on both counts. Can we get a TODO?
> --
> Decibel!, aka Jim C. Nasby, Database Architect  decibel@decibel.org
> Give your computer some brain candy! www.distributed.net Team #1828
>
>
>




pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: [hensa22@yahoo.es: Re: [pgsql-es-ayuda] SLL error 100% cpu]
Next
From: Tatsuo Ishii
Date:
Subject: Re: Proposal: new large object API