Overview and usage of COMMIT in Oracle Form

1. COMMIT_FORM and COMMIT
Both form and database are submitted. Submit the data changes in form to the background database, and submit the data in the database.

2. DO_KEY ('commit _ form ')
It will first execute the code in the KEY-COMMIT trigger. Without this trigger, it will perform the same operations as COMMIT_FORM.

3. FORMS_DLL ('commit ')
Only the insert, update, and delete statements in the Code are submitted. The data on the form is not submitted.
DG mentioned:
Replace COMMIT with do_key ('commit _ form'), This routine raises the exception FORM_TRIGGER_FAILURE if there is an invalid record.
Trigger execution sequence in 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 "quietly" Submit. If commit_form is used, the message "no changes need to be saved" or "XXX record saved" is displayed ". You can call the function if you do not want to prompt
App_form.quietcommit. Because it is a function, a variable needs to be defined to receive the return value. The return value type is boolean. If it is true, the return value is successful. Otherwise, the commit fails.
The following process can be called to change the system message level to a lower level:
Copy codeThe Code is 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;