summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorDaniele Varrazzo <daniele.varrazzo@gmail.com>2017-02-24 16:53:32 +0000
committerDaniele Varrazzo <daniele.varrazzo@gmail.com>2017-02-24 16:53:32 +0000
commitc871c49f55e2e1787f1c2d7edeaf0f8f5c876db3 (patch)
tree87c04eddfeef6890f90d06c7a9893134447401ef
parent72f74d1f410c26ee4c410bef1ffcdcee4b1c0833 (diff)
downloadpsycopg2-c871c49f55e2e1787f1c2d7edeaf0f8f5c876db3.tar.gz
Dropped reference to "isolation level autocommit" in docs
-rw-r--r--doc/src/usage.rst4
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/src/usage.rst b/doc/src/usage.rst
index 6cb038b..cde0242 100644
--- a/doc/src/usage.rst
+++ b/doc/src/usage.rst
@@ -776,8 +776,8 @@ you may decrease this value if you are dealing with huge records.
Named cursors are usually created :sql:`WITHOUT HOLD`, meaning they live only
as long as the current transaction. Trying to fetch from a named cursor after
-a `~connection.commit()` or to create a named cursor when the `connection`
-transaction isolation level is set to `AUTOCOMMIT` will result in an exception.
+a `~connection.commit()` or to create a named cursor when the connection
+is in `~connection.autocommit` mode will result in an exception.
It is possible to create a :sql:`WITH HOLD` cursor by specifying a `!True`
value for the `withhold` parameter to `~connection.cursor()` or by setting the
`~cursor.withhold` attribute to `!True` before calling `~cursor.execute()` on