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 connection are closed, except cursors that are defined
Cursors that are defined
WITH HOLDremain open, but the cursor is no longer positioned on a row. A
FETCHstatement is required to position the cursor on a row before another
UPDATE CURRENTstatement can be executed.
If there is no currently active transaction, any cursors opened by the current ident are closed (except
), but the
COMMITstatement is otherwise ignored. No error code is returned in this case.
BACKUPtransaction performs online backup for all databanks for which a
CREATE BACKUPcommand has been performed since
START BACKUP. Please note that this command may be lengthy if backups for large databank files are made.
COMMITstatement cannot be used in a result set procedure because this would close the cursor which is calling it.
COMMITstatement cannot be used within an atomic compound SQL statement, see COMPOUND STATEMENT.
COMMIT BACKUPstatement can only be used when a corresponding
START BACKUPcommand has been given. The
COMMIT BACKUPstatement is not supported in procedural mode.
See the Mimer SQL Programmer's Manual, 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;
Mimer Information Technology AB
Voice: +46 18 780 92 00
Fax: +46 18 780 92 40