RDB/VMS SQL SET_ALL_CONSTRAINT — VMS RDB_4.2
SET ALL CONSTRAINTS -+-> IMMEDIATE --+-> ;
+-> DEFERRED ---+
+-> ON ---------+
+-> OFF --------+
Additional information available:
More Information
Controls constraint checking for constraints that are evaluated at commit time. (This statement has no effect on constraints that are evaluated at verb time.) A major use of the SET ALL CONSTRAINTS statement is to permit evaluation of these constraints at intervals before the transaction is committed. The default setting for the SET ALL CONSTRAINTS statement is OFF (that is, constraint evaluation is deferred until commit time) -- unless you have specified otherwise with the /SQLOPTIONS=(CONSTRAINTS=ON) qualifier on the SQL precompiler command line, or with the /CONSTRAINTS=ON qualifier on the SQL module language command line. Setting constraints ON causes all the affected constraints to be evaluated when the SET ALL CONSTRAINTS ON statement executes and causes any constraints selected for deferred evaluation by the execution of an SQL statement to be evaluated at the end of the SQL statement (until you SET ALL CONSTRAINTS OFF or until the transaction completes with a commit or rollback operation). You can use the IMMEDIATE keyword instead of ON. Setting constraints OFF causes constraint evaluation to be deferred until commit time. This is the initial and default setting for the SET ALL CONSTRAINTS statement. You can use the DEFERRED keyword instead of OFF. If a transaction has been declared but is not active when the SET ALL CONSTRAINTS statement is executed, SQL starts the declared transaction.