Effects of Aborted Transactions
When a statement or transaction is aborted (due to an application or the DBMS itself), the following occurs:
• Rolling back a single statement does not cause the DBMS to release any locks held by the transaction. Locks are released when the transaction ends.
• If cursors are open, the entire transaction is always aborted.
• When an entire transaction is aborted, all open cursors are closed, and all prepared statements are invalidated.
When writing embedded SQL applications, your application must include logic for handling operator interrupts. By default, if the application is aborted during a transaction, the transaction is rolled back. This also applies to Ingres tools. For example, if you abort Query-By-Forms (QBF) while it is performing an update, the update is rolled back.