Transactional triggers fire in response to a wide variety of events that occur as a form interacts with the data source.
Trigger |
Typical Usage |
---|---|
Replace the default Oracle Forms processing for handling deleted records during transaction posting. |
|
Replace the default Oracle Forms processing for handling inserted records during transaction posting. |
|
Replace the default Oracle Forms processing for locking rows in the database. |
|
Replace the default Oracle Forms processing for connecting to ORACLE, especially for a form that does not require a database connection or for connecting to a non-ORACLE data source. |
|
Replace the default Oracle Forms processing for logout from ORACLE. |
|
Replace the default Oracle Forms processing for handling updated records during transaction posting. |
|
Augment default Oracle Forms processing following a database commit. |
|
Audit transactions following the deletion of a row from the database. |
|
Augment the default Oracle Forms commit statement prior to committing a transaction. |
|
Audit transactions following the insertion of a row in the database. |
|
Audit transactions following the updating of a row in the database. |
|
Perform an action immediately before the Post and Commit Transactions process, when Oracle Forms determines that there are changes in the form to post or to commit. |
|
Manipulate a record prior to its being deleted from the database during the default Post and Commit Transactions process; for example, to prevent deletion of the record if certain conditions exist. |
|
Manipulate a record prior to its being inserted in the database during the default Post and Commit Transactions process. |
|
Validate or modify a record prior to its being updated in the database during the default Post and Commit Transactions process. |
Note: This is only a partial List of the transactional triggers available. Many of the triggers not shown here are On-event triggers that exist primarily for applications that will run against a non-ORACLE data source.