From fc5cc1df01fafcbd62ceb66ada81a0341e467ae7 Mon Sep 17 00:00:00 2001 From: Daniele Varrazzo Date: Wed, 15 Aug 2012 12:28:13 +0100 Subject: [PATCH] Fixed note on rollback on close in the doc 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. --- doc/src/usage.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/src/usage.rst b/doc/src/usage.rst index a38a8442..1ab64197 100644 --- a/doc/src/usage.rst +++ b/doc/src/usage.rst @@ -521,7 +521,7 @@ the `~connection.commit()` or `~connection.rollback()` method. Committed changes are immediately made persistent into the database. Closing the connection using the `~connection.close()` method or destroying the 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 commands executed will be immediately committed and no rollback is possible. A