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

From Decibel!
Subject Re: Proposal for db level triggers
Date
Msg-id EB824DFB-14C4-4094-9A21-C81796E16045@decibel.org
Whole thread Raw
In response to Re: Proposal for db level triggers  (James Mansion <james@mansionfamily.plus.com>)
Responses Re: Proposal for db level triggers
Re: Proposal for db level triggers
List pgsql-hackers
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: Hans-Juergen Schoenig
Date:
Subject: Re: [Fwd: Re: [PATCHES] 64-bit CommandIds]
Next
From: Zdenek Kotala
Date:
Subject: Re: How large file is really large - pathconf results