Hi,

> > > >Triggers for integrity ... ouch.
> > >
> > > Martijn, how do you think we managed before IB introduced formal ref
> > > integrity
> >
> > Almost not at all :) :)
> >
> > >and Frigidaire invented the washing machine? (Oh to be so young!)
> > >
> > > :-)
> >
> > Declarative RI beats triggers anyday, anytime.
>
> Unless there is a bug in the engine that screws up your data when using

RI.

> <g>
>
> Seriously, besides the argument listed by Alan regarding your statement
> about other programs or tools being used to access data, is there any

other

> reason to use built in RI other than it is there? (Kind of like climbing

the

> mountain, huh? :)
>
> For me, the thought of an RI bug being introduced in a future version is
> more likely (and beyond my control) than a bug in my code that simply

loops

> through deleting child records when a master record is deleted. I only use

The use of RI has not as much to do with deleting "child" rows than with
preventing the deletion of "master" rows when a child exists...

You SHOULD use RI almost because of the same reasons why you use
PKs and such...

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