|Subject||Re: [Firebird-Architect] Cross table constraints was Nulls in CHECK Constraints|
> Among my questions are:IMO, yes.
> 1) Does the standard require that check constraints be
> valid at all times or only when rows of the constrained
> table are altered? Probably the former...
> 2) Does it make sense to get V2, V1.5.3, and Vulcan out
> and then have a serious talk about how constraints - row,
> verb, and deferred - should be implemented?
Database Workbench - tool for InterBase, Firebird, MySQL, Oracle & MS SQL
Database development questions? Check the forum!