psycopg/psycopg2
1
1
Fork 0
mirror of https://github.com/psycopg/psycopg2.git synced 2025-10-30 23:37:29 +03:00
Code Issues Packages Projects Releases Wiki Activity

Document that named cursors don't raise an exception going out-of-bound

Browse Source 
See issue #174 for the details.

Conflicts:

	doc/src/cursor.rst
This commit is contained in:
Daniele Varrazzo 2013-10-16 19:08:45 +01:00
parent b95bb2c641
commit 970bb1d1b1
1 changed files with 7 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
doc/src/cursor.rst
View File

@ -296,9 +296,6 @@ The ``cursor`` class
`~psycopg2.ProgrammingError` is raised and the cursor position is `~psycopg2.ProgrammingError` is raised and the cursor position is
not changed. not changed.
The method can be used both for client-side cursors and
:ref:`server-side cursors <server-side-cursors>`.
.. note:: .. note::
According to the |DBAPI|_, the exception raised for a cursor out According to the |DBAPI|_, the exception raised for a cursor out
@ -310,6 +307,13 @@ The ``cursor`` class
except (ProgrammingError, IndexError), exc: except (ProgrammingError, IndexError), exc:
deal_with_it(exc) deal_with_it(exc)
The method can be used both for client-side cursors and
:ref:`server-side cursors <server-side-cursors>`. Server-side cursors
can usually scroll backwards only if declared `~cursor.scrollable`.
Moving out-of-bound in a server-side cursor doesn't result in an
exception, if the backend doesn't raise any (Postgres doesn't tell us
in a reliable way if we went out of bound).
.. attribute:: arraysize .. attribute:: arraysize