Download Mimer SQL Reference Manual - Department of Information Technology

SQL statement descriptions
6-29
COMMIT
Commits the current transaction.
ªÞÞÞ COMMIT ÞÞ½ÞÞÞÞÞÞÞÞÞÞÞÞÞÞÞÞÞ½ÞÞÞÞÞÞÞÞÞÞÞÞÞÞÞÞÞÞÞÞÞÞÞÞÞÞÞÞÞÞÞÞÞÞÞÞÞÃ
¦
¦
ðÞÞ WORK ÞÞÞÞÞÞÞÞÞ¶
¦
¦
ðÞÞ TRANSACTION ÞÞ¶
¦
¦
÷ÞÞ BACKUP ÞÞÞÞÞÞÞç
Usage
Embedded/Interactive/Procedural.
Description
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.
Restrictions
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.
Notes
See Chapter 6 of the Mimer SQL Programmer’s Manual for a detailed
discussion of transaction control.
Mimer SQL version 8.2
Reference Manual