.. changelog::
:version: 0.8.2
+ .. change::
+ :tags: feature, postgresql
+ :tickets: 2072
+
+ Added support for "AUTOCOMMIT" isolation when using the psycopg2
+ DBAPI. The keyword is available via the ``isolation_level``
+ execution option. Patch courtesy Roman Podolyaka.
+
.. change::
:tags: bug, orm
:tickets: 2759
:func:`.create_engine` accepts an ``isolation_level`` parameter which results
in the command ``SET SESSION CHARACTERISTICS AS TRANSACTION ISOLATION LEVEL
<level>`` being invoked for every new connection. Valid values for this
-parameter are ``READ COMMITTED``, ``READ UNCOMMITTED``, ``REPEATABLE READ``,
+parameter include ``READ COMMITTED``, ``READ UNCOMMITTED``, ``REPEATABLE READ``,
and ``SERIALIZABLE``::
engine = create_engine(
When using the psycopg2 dialect, a psycopg2-specific method of setting
transaction isolation level is used, but the API of ``isolation_level``
-remains the same - see :ref:`psycopg2_isolation`.
+remains the same. The psycopg2 dialect also includes support
+for ``AUTOCOMMIT`` isolation - see :ref:`psycopg2_isolation`.
Remote / Cross-Schema Table Introspection
* isolation_level - Set the transaction isolation level for the lifespan of a
:class:`.Connection` (can only be set on a connection, not a statement
or query). This includes the options ``SERIALIZABLE``, ``READ COMMITTED``,
- ``READ UNCOMMITTED`` and ``REPEATABLE READ``.
+ ``READ UNCOMMITTED``, ``REPEATABLE READ``, and ``AUTOCOMMIT``.
+
+ .. versionadded:: 0.8.2 support for AUTOCOMMIT isolation level when using
+ psycopg2.
+
* stream_results - Enable or disable usage of server side cursors.
If ``None`` or not set, the ``server_side_cursors`` option of the
:class:`.Engine` is used.