Aborts the current transaction.
The current transaction is aborted. No database alterations requested in the transaction build-up are executed.
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 ROLLBACK statement is otherwise ignored. No error code is returned in this case.
When a BACKUP transaction is rolled back, all files created with CREATE BACKUP are deleted.
The ROLLBACK statement cannot be used in a result-set procedure.
The ROLLBACK statement cannot be used within an atomic compound SQL statement, see COMPOUND STATEMENT.
The ROLLBACK BACKUP statement must be used to abort a BACKUP transaction.
The ROLLBACK BACKUP statement is not supported in procedural usage contexts.
See the Mimer SQL Programmer's Manual, chapter 9, Transaction Handling and Database Security, for a more detailed discussion of transaction handling.
ExampleLOOP EXEC SQL FETCH C1 INTO :var1,:var2,...,:varn; DISPLAY var1,var2,...,varn; PROMPT "Update row?"; EXIT WHEN ANSWER = "yes"; EXEC SQL ROLLBACK; END LOOP;
For more information, see the Mimer SQL Programmer's Manual, chapter 9, Transaction Control Statements.
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