Commits the current transaction.
The current transaction is terminated. Database alterations requested in the transaction build-up are executed against the database, provided that no transaction conflict is detected.
If a transaction conflict is detected, no changes are made in the database, and an error code is set to indicate a transaction conflict. The intention list established during the transaction build-up is dropped.
All cursors opened by the current ident are closed.
If there is no currently active transaction, any cursors opened by the current ident are closed, but the COMMIT statement is otherwise ignored. No error code is returned in this case.
Committing a BACKUP transaction performs online backup for all databanks for which a CREATE BACKUP command has been performed since START BACKUP. Please note that this command may be lengthy if backups for large databank files are made.
The COMMIT statement cannot be used in a result set procedure because this would close the cursor which is calling it.
The COMMIT statement cannot be used within an atomic compound SQL statement, see COMPOUND STATEMENT.
The COMMIT BACKUP statement can only be used when a corresponding START BACKUP command has been given. The statement is not supported in procedural mode.
See the Mimer SQL Programmer's Manual, chapter 9, Transaction Handling and Database Security, for a detailed discussion of transaction control.
ExampleEXEC SQL SET TRANSACTION START EXPLICIT LOOP EXEC SQL FETCH C1 INTO :var1,:var2,...,:varn; DISPLAY var1,var2,...,varn; PROMPT "Update row?"; EXIT when answer = "yes"; END LOOP EXEC SQL START; EXEC SQL UPDATE table SET ... WHERE col1 = :var1, col2 = :var2, ... EXEC SQL COMMIT;
EXTENDED Support for the BACKUP and TRANSACTION keywords is a Mimer SQL extension.
Upright Database Technology AB
Voice: +46 18 780 92 00
Fax: +46 18 780 92 40