Executing one or more DML statements causes a transaction to be set up. The data changes represented by the DML statement(s) do not become definitive and visible to all users until the transaction is committed.
Until you commit, you have the option to revert or roll back to the state of the database that occurred prior to your first DML statement.
The USoft Rules Engine supports the COMMIT and ROLLBACK transaction control statements.
This statement commits data changes of the current transaction to the RDBMS so that they become visible to other users and can no longer be rolled back. These data changes include any knock-on data changes causes by constraints having been triggered during the current transaction.
This statement activates table constraints with Deferred = Post Commit (if any).
This statement rolls back all data changes of the current transaction. These data changes include any knock-on data changes causes by constraints having been triggered during the current transaction.
Queries and subqueries
Method invocation statements