1. Commit_form and commits
Both the form and the database are submitted. Submit to the background database for data changes above the form, while the database submits the data.
2. Do_key (' Commit_form ')
It will first execute the code inside the Key-commit trigger, and if it does not have the trigger, it will do the commit_form-like operation.
3. Forms_dll (' COMMIT ')
Commits only to insert, UPDATE, DELETE statements in code, and data on form is not submitted.
DG inside mentions:
Replace COMMIT with Do_key (' Commit_form '), this routine raises the exception form_trigger_failure if there be an invalid R Ecord.
Trigger execution order at commit:
(1). Key-commit
(2). Pre-commit
(3). Pre/on/post DELETE
(4). Pre/on/post UPDATE
(5). Pre/on/post INSERT
(6). On-commit
(7). Post DataBase Commit
4. Quietcommit
Oracle form "silently" commits. If you use Commit_form, you will be prompted with "no modifications needed to be saved" or "XXX record saved". If you don't want to be prompted, you can call the function
App_form.quietcommit. Because it is a function, you need to define a variable to receive the return value, the return value type is Boolean, the success when true, or commit failure.
Changing the system's message level to a lower level also calls the following procedure:
Copy Code code as follows:
PROCEDURE Docommit is
Old_level VARCHAR2 (2);
BEGIN
Old_level: = name_in (' System.message_level ');
Copy (' 5 ', ' system.message_level ');
COMMIT;
Copy (Old_level, ' system.message_level ');
End;
