Subject | Re: [firebird-support] Triggers and referential integrity |
---|---|
Author | Tim Ledgerwood |
Post date | 2003-10-21T08:42:56Z |
Hi Martijn,
:-) I already make extensive use of domains with check constraints - the
primary table has every field except the primary key field as a domain with
a check constraint.
As I said, the problem isn't the Inserts so much as the deletes. In the
case of a tax table (we also have three here), how do I prevent the user
from deleting a tax type if there are any records in the primary table with
that tax type?
Regards
Tim
[Non-text portions of this message have been removed]
:-) I already make extensive use of domains with check constraints - the
primary table has every field except the primary key field as a domain with
a check constraint.
As I said, the problem isn't the Inserts so much as the deletes. In the
case of a tax table (we also have three here), how do I prevent the user
from deleting a tax type if there are any records in the primary table with
that tax type?
Regards
Tim
[Non-text portions of this message have been removed]