ODBC can run in two modi. By default, all update actions are
immediately committed on the server. Using odbc_set_connection/2
this behaviour can be switched off, after which each SQL statement that
can be inside a transaction implicitly starts a new transaction. This
transaction can be ended using odbc_end_transaction/2.
- odbc_end_transaction(+Connection,
+Action)
- End the currently open transaction if there is one. Using Action
commit pending updates are made permanent, using
rollback they are discarded.
The ODBC documentation has many comments on transaction management
and its interaction with database cursors.
