Constraint Tests

Previous Next

See Also

Restrictive constraints that concern more than one record and cannot be handled before the actual storage of one of those records, are classified as constraint tests.

Constraint tests occur at commit time and are registered in BenchMark profiler output as CONSTRAINT_TEST. In constraint tests, constraint evaluation occurs because of one or more row events "touched" the constraint columns earlier in the transaction.

Restrictive, non-transitional, multi-record constraints are handled as constraint tests.

If a constraint is handled as constraint test, this is signaled in the violation list at record validation time. The violation list can be viewed by selecting File, Transactions from the menu bar.