Subject RE: [Firebird-Architect] Nulls in CHECK Constraints
Author Claudio Valderrama C.
> -----Original Message-----
> From:
> []On Behalf Of Martijn Tonies
> Sent: MiƩrcoles, 26 de Octubre de 2005 6:38
> Might be, but given that our CHECKs are only evaluated on insert/update
> (and not even on DELETE), could make them useless in certain occasions
> when referring to other tables.

The code has existed always to generate checks for DELETE...
but it has been always commented, too. We got it this way from Borland.

Can you explain how a check on delete is necessary? I don't get the idea.
Maybe if it references another table, but a thing like check (a > 0) has
little sense when deleting. It should have been validated at insertion or
update time.