Subject | Re: CHECK Constraints (was: Re: [firebird-support] Re: Checking periods don't overlap) |
---|---|
Author | Jerome Bouvattier |
Post date | 2004-06-15T18:29:47Z |
Hi,
=> Ann
Let's suppose CHECK constraints now operate in the system transaction
context, don't we still miss something to cover all the possibilities, in
that CHECK constraints are not triggered for deletions.
For example, if you want to implement custom RI, master table must search
the detail table for detail records, and if any are found either cascade
delete them or trigger an error.
Regards.
--
Jerome
> Thanks for acknowledging that this is a problem Ann.Indeed.
>
> I feel a lot better knowing that's recognised as something 'bad'.
> Gives you confidence that the developers are receptive.
=> Ann
Let's suppose CHECK constraints now operate in the system transaction
context, don't we still miss something to cover all the possibilities, in
that CHECK constraints are not triggered for deletions.
For example, if you want to implement custom RI, master table must search
the detail table for detail records, and if any are found either cascade
delete them or trigger an error.
Regards.
--
Jerome