> > 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 ...
> >
> > Regards,
> > Thomas Steinmaurer
> > http://www.iblogmanager.com
>
> Do I understand well if I say that the above mean that the order of
> evaluation is the following :
>
> all BeforeInsert triggers
> check constraints
> all AfterInsert triggers.
>
> IOW, I should be able to transform unacceptable data according to the
> constraints to acceptable data in SQL code placed in before...
> triggers.

Yes, you should be able to do this.

But there is a 'but':
IB 6.5 and IB 6.0.2.0 fire CHECK CONSTRAINTS before any
user defined BEFORE [OPERATION] triggers. And yes, this is
a bug.

Firebird does not suffer from this problem.

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."