Tree @9e2744a (Download .tar.gz)
- ..
- aq.rst
- batch_statement.rst
- bind.rst
- connection_handling.rst
- cqn.rst
- exception_handling.rst
- globalization.rst
- ha.rst
- initialization.rst
- installation.rst
- introduction.rst
- json_data_type.rst
- lob_data.rst
- plsql_execution.rst
- soda.rst
- sql_execution.rst
- startup.rst
- tracing_sql.rst
- tuning.rst
- txn_management.rst
- xml_data_type.rst
txn_management.rst @9e2744a — view markup · raw · history · blame
Transaction Management
A database transaction is a grouping of SQL statements that make a logical data change to the database.
When :meth:`Cursor.execute()` executes a SQL statement, a transaction is started or continued. By default, cx_Oracle does not commit this transaction to the database. The methods :meth:`Connection.commit()` and :meth:`Connection.rollback()` methods can be used to explicitly commit or rollback a transaction:
cursor.execute("INSERT INTO mytab (name) VALUES ('John')") connection.commit()
When a database connection is closed, such as with :meth:`Connection.close()`, or when variables referencing the connection go out of scope, any uncommitted transaction will be rolled back.
Autocommitting
An alternative way to commit is to set the attribute :attr:`~Connection.autocommit` of the connection to True. This ensures all :ref:`DML <dml>` statements (INSERT, UPDATE etc) are committed as they are executed. Unlike :meth:`Connection.commit()`, this does not require an additional :ref:`round-trip <roundtrips>` to the database so it is more efficient when used appropriately.
Note that irrespective of the autocommit value, Oracle Database will always commit an open transaction when a DDL statement is executed.
When executing multiple DML statements that constitute a single transaction, it is recommended to use autocommit mode only for the last DML statement in the sequence of operations. Unnecessarily committing causes extra database load, and can destroy transactional consistency.
The example below shows a new customer being added to the table CUST_TABLE. The corresponding SALES table is updated with a purchase of 3000 pens from the customer. The final insert uses autocommit mode to commit both new records:
# Add a new customer idVar = cursor.var(int) connection.autocommit = False # make sure any previous value is off cursor.execute(""" INSERT INTO cust_table (name) VALUES ('John') RETURNING id INTO :bvid""", bvid=idVar) # Add sales data for the new customer and commit all new values idVal = idVar.getvalue()[0] connection.autocommit = True cursor.execute("INSERT INTO sales_table VALUES (:bvid, 'pens', 3000)", bvid=idVal)
Explicit Transactions
The method :meth:`Connection.begin()` can be used to explicitly start a local or global transaction.
Without parameters, this explicitly begins a local transaction; otherwise, this explicitly begins a distributed (global) transaction with the given parameters. See the Oracle documentation for more details.
Note that in order to make use of global (distributed) transactions, the attributes :attr:`Connection.internal_name` and :attr:`Connection.external_name` attributes must be set.