In the solidDB DML execution model, the solidDB server performs a number of validation checks before executing data manipulation statements (INSERT, UPDATE, or DELETE). The execution for data validation, trigger execution, and integrity constraint checking for a single DML statement is completed in the following order:
1 Values that are part of the statement (that is, not bound) are validated. This includes null value checking, data type checking, and so on.
2 Table level security checks are performed.
3 For each row affected by the SQL statement, actions are performed in the following order:
a Column-level security checks.
b Any BEFORE row trigger is executed, see CREATE TRIGGER.
c Values are validated, if values are bound in. This includes null value checks, data type checking, and size checking (for example, checking if the character string is too long).
Size checking is performed even for values that are not bound.
d INSERT, UPDATE, and DELETE statements are executed.
e Any AFTER row trigger is executed, see CREATE TRIGGER.
4 The statement is committed, including the following actions:
a concurrency conflict checks,
b duplicate value checks,
c referential integrity checks on invoking DML.
Note A trigger itself can cause DML to be executed, in which case, the data validation, trigger execution, and integrity constraint checking for the DML statement is completed in the same order.