Re: Proposal for db level triggers

From: alfranio(at)lsd(dot)di(dot)uminho(dot)pt
To: "Decibel!" <decibel(at)decibel(dot)org>
Cc: "James Mansion" <james(at)mansionfamily(dot)plus(dot)com>, "PostgreSQL-development" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Proposal for db level triggers
Date: 2008-03-21 19:58:44
Message-ID: 40937.192.168.82.158.1206129524.squirrel@webmail.lsd.di.uminho.pt
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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(at)decibel(dot)org
> Give your computer some brain candy! www.distributed.net Team #1828
>
>
>

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2008-03-21 21:18:59 Re: Logging conflicted queries on deadlocks
Previous Message Bruce Momjian 2008-03-21 19:34:22 Re: [hensa22@yahoo.es: Re: [pgsql-es-ayuda] SLL error 100% cpu]