Constraint Evaluation: Overview

See Also

Here is an overview of the constraint execution order for non-transitional constraints of the Rules Engine. Single-record constraints are handled at record validation time. First the corrections are made and then restrictions are tested.

The next step is that the record is physically stored.

Also at record validation time, and just after record storage, corrective multi-record constraints are evaluated. This means that the storage of one record can lead to the storage of other records in other tables.

Corrective (single- and multi-record) constraints will lead to re-consideration of all domain and column checks and corrections.

Restrictive multi-record constraints are deferred to commit time. The same applies to constraints that are manually set to Deferred.

At record validation time, a list is compiled of all constraints that, as a result of the record validation, must be evaluated at commit time.

Execution Order of Constraints