Skip Headers
Oracle® Application Development Framework Developer's Guide For Forms/4GL Developers
10g (10.1.3.1.0)

Part Number B25947-01
Go to Documentation Home
Home
Go to Book List
Book List
Go to Table of Contents
Contents
Go to Index
Index
Go to Master Index
Master Index
Go to Feedback page
Contact Us

Go to previous page
Previous
Go to next page
Next
View PDF

C.4 Transaction "Post" Processing (Record Cache)

Table C-4 ADF Equivalents for Oracle Forms Transactional Triggers

Forms Trigger ADF Equivalent

PRE-COMMIT

Execute code before commencing processing of the changed rows in all data blocks in the transaction.

Override commit() method in a custom DBTransactionImpl class and write code before calling the super.

Note:

See this article for an overview of creating and using a custom DBTransaction implementation.

PRE-INSERT

Execute code before NEW row in the datablock is INSERTed into the database during "post" processing.

Override doDML() method in your entity class and if the operation equals DML_INSERT then write code before calling the super.

ON-INSERT

Override default processing for INSERTing a NEW row into the database during "post" processing.

Override doDML() method in your entity class and if the operation equals DML_INSERT then write code instead of calling the super.

POST-INSERT

Execute code after NEW row in the datablock is INSERTed into the database during "post" processing.

Override doDML() method in your entity class and if the operation equals DML_INSERT then write code after calling the super.

PRE-DELETE

Execute code before row removed from the datablock is DELETEd from the database during "post" processing.

Override doDML() method in your entity class and if the operation equals DML_DELETE then write code before calling the super.

ON-DELETE

Override default processing for DELETE-ing a row removed from the datablock from the database during "post" processing.

Override doDML() method in your entity class and if the operation equals DML_DELETE then write code instead of calling the super.

POST-DELETE

Execute code after row removed from the datablock is DELETEd from the database during "post" processing.

Override doDML() method in your entity class and if the operation equals DML_DELETE then write code after calling the super.

PRE-UPDATE

Execute code before row changed in the datablock is UPDATEd in the database during "post" processing.

Override doDML() method in your entity class and if the operation equals DML_UPDATE then write code before calling the super.

ON-UPDATE

Override default processing for UPDATE-ing a row changed in the datablock from the database during "post" processing.

Override doDML() method in your entity class and if the operation equals DML_UPDATE then write code instead of calling the super.

POST-UPDATE

Execute code after row changed in the datablock is UPDATEd in the database during "post" processing.

Override doDML() method in your entity class and if the operation equals DML_UPDATE then write code after calling the super.

POST-FORMS-COMMIT

Execute code after Forms has "posted" all necessary rows to the database, but before issuing the data COMMIT to end the transaction.

If you want a single block of code for the whole transaction, you can override the doCommit() method in a custom DBTransactionImpl object and write some code before calling super. To execute entity-specific code before commit for each affected entity in the transaction, override the beforeCommit() method on your entity object and write some code there.

POST-DATABASE-COMMIT

Execute code after database transaction has been committed.

Override commit() method in a custom DBTransactionImpl class and write code after calling the super.