psycopg/psycopg2
1
1
Fork 0
mirror of https://github.com/psycopg/psycopg2.git synced 2024-11-11 19:46:36 +03:00
Code Issues Packages Projects Releases Wiki Activity

Fixed note on rollback on close in the doc

Browse Source 
It's not like we call "rollback()": we close the connection and the
backend rolls back on its own. It may have differences, e.g. conn poolers.
This commit is contained in:
Daniele Varrazzo 2012-08-15 12:28:13 +01:00
parent 7cb754fbc9
commit fc5cc1df01
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
doc/src/usage.rst
View File

@ -521,7 +521,7 @@ the `~connection.commit()` or `~connection.rollback()` method. Committed
changes are immediately made persistent into the database. Closing the changes are immediately made persistent into the database. Closing the
connection using the `~connection.close()` method or destroying the connection using the `~connection.close()` method or destroying the
connection object (using `!del` or letting it fall out of scope) connection object (using `!del` or letting it fall out of scope)
will result in an implicit `!rollback()` call. 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