> > > Btw, if you want to track *committed* changes, then use AFTER
> > [OPERATION]
> > > triggers instead of BEFORE [OPERATION] triggers.
> >
> > I do not believe that AFTER [OPERATION] has anything to do with
> > COMMITting -
> > they will fire just, eh, after the operation :)
>
> Consistent would be the better term ;-). Tracking changes in a
> BEFORE [OPERATION] trigger would mean, that data which for example
> don't fulfill a CHECK constraint would be tracked too ...

ok :)

Jeez, why are you so obsessed with tracking changes *grin*

> Regards,
> Thomas Steinmaurer
> http://www.iblogmanager.com

Martijn Tonies
InterBase Workbench - the developer tool for InterBase and Firebird
http://www.interbaseworkbench.com

Upscene Productions
http://www.upscene.com

"This is an object-oriented system.
If we change anything, the users object."