psycopg/psycopg2
1
1
Fork 0
mirror of https://github.com/psycopg/psycopg2.git synced 2025-08-01 02:50:08 +03:00
Code Issues Packages Projects Releases Wiki Activity

Add calling stored procedurs that have transaction control to list of SQL commands to be run with autocommit set to false.

Browse Source
This commit is contained in:
David Rader 2020-04-02 14:56:24 -04:00
parent 2bee47efac
commit 0f8f8f386f
3 changed files with 7 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
doc/src/connection.rst
View File

@ -431,8 +431,8 @@ The ``connection`` class
invoked to terminate the transaction. invoked to terminate the transaction.
The autocommit mode is useful to execute commands requiring to be run The autocommit mode is useful to execute commands requiring to be run
outside a transaction, such as :sql:`CREATE DATABASE` or outside a transaction, such as :sql:`CREATE DATABASE`,
:sql:`VACUUM`. :sql:`VACUUM`, or calling stored procedures with transaction control inside.
The default is `!False` (manual commit) as per DBAPI specification. The default is `!False` (manual commit) as per DBAPI specification.

5
doc/src/extensions.rst
View File

@ -743,8 +743,9 @@ methods. The level can be set to one of the following constants:
No transaction is started when commands are executed and no No transaction is started when commands are executed and no
`~connection.commit()` or `~connection.rollback()` is required. `~connection.commit()` or `~connection.rollback()` is required.
Some PostgreSQL command such as :sql:`CREATE DATABASE` or :sql:`VACUUM` Some PostgreSQL commands such as :sql:`CREATE DATABASE`, :sql:`VACUUM`,
can't run into a transaction: to run such command use:: or calling stored procedures with transaction control inside
can't run inside a transaction: to run such command use::
>>> conn.set_isolation_level(ISOLATION_LEVEL_AUTOCOMMIT) >>> conn.set_isolation_level(ISOLATION_LEVEL_AUTOCOMMIT)

3
doc/src/usage.rst
View File

@ -757,7 +757,8 @@ will result in an implicit rollback.
It is possible to set the connection in *autocommit* mode: this way all the It is possible to set the connection in *autocommit* mode: this way all the
commands executed will be immediately committed and no rollback is possible. A commands executed will be immediately committed and no rollback is possible. A
few commands (e.g. :sql:`CREATE DATABASE`, :sql:`VACUUM`...) require to be run few commands (e.g. :sql:`CREATE DATABASE`, :sql:`VACUUM`, calling stored
procedures with transaction control inside...) require to be run
outside any transaction: in order to be able to run these commands from outside any transaction: in order to be able to run these commands from
Psycopg, the connection must be in autocommit mode: you can use the Psycopg, the connection must be in autocommit mode: you can use the
`~connection.autocommit` property. `~connection.autocommit` property.