A script-enabled browser is required for this page to function properly.

Pre-Commit Trigger

Description

Fires once during the Post and Commit Transactions process, before Oracle Forms processes any records to change. Specifically, it fires after Oracle Forms determines that there are inserts, updates, or deletions in the form to post or commit, but before it commits the changes. The trigger does not fire when there is an attempt to commit, but validation determines that there are no changed records in the form.

Pre-Commit does fire in case of Post when there is no change in the form, but there are uncommited changes in the database.

Definition Level form

Legal Commands

SELECT statements, DML statements (DELETE, INSERT, UPDATE), unrestricted Built-ins

Enter Query Mode no

Usage Notes

Use a Pre-Commit trigger to perform an action, such as setting up special locking requirements, at any time a database commit is going to occur.

On Failure

The Post and Commit process fails: No records are written to the database and focus remains in the current item.

Note: If you perform DML in a Pre-Commit trigger and the trigger fails, you must perform a manual rollback, because Oracle Forms does not perform an automatic rollback. To prepare for a possible manual rollback, save the savepoint name in an On-Savepoint trigger, using GET_APPLICATION_PROPERTY (Savepoint_Name). Then you can roll back using ISSUE_ROLLBACK (Savepoint_Name).

Fires In

Post and Commit Transactions