Re: Proposal for db level triggers

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