Post-Store Record Validation After Update

Previous Next

After a record has been updated:

1.For restrictive, non-transitional, multi-record constraints, the Rules Engine determines the primary key values of the driving table, if they are not known. In some cases, a constraint key query is needed to retrieve these primary key values. Refer to "Driving Tables" and "Constraint Key Query" for details.
2.Cardinality checks for relationships in which this record is a child record are generated, but are kept until commit.
3.If primary key columns have changed, cascading and nullifying update rules are executed.
4.Corrective multi-record constraints that have not been set to Deferred are evaluated. These corrections may lead to new row events.

The non-transitional constraints are evaluated first, then the transitional constraints.