From 970bb1d1b1f808e187a0a6f5c1f8dbd1dd4b2c98 Mon Sep 17 00:00:00 2001 From: Daniele Varrazzo Date: Wed, 16 Oct 2013 19:08:45 +0100 Subject: [PATCH] Document that named cursors don't raise an exception going out-of-bound See issue #174 for the details. Conflicts: doc/src/cursor.rst --- doc/src/cursor.rst | 10 +++++++--- 1 file changed, 7 insertions(+), 3 deletions(-) diff --git a/doc/src/cursor.rst b/doc/src/cursor.rst index 4b8495ae..36768232 100644 --- a/doc/src/cursor.rst +++ b/doc/src/cursor.rst @@ -296,9 +296,6 @@ The ``cursor`` class `~psycopg2.ProgrammingError` is raised and the cursor position is not changed. - The method can be used both for client-side cursors and - :ref:`server-side cursors `. - .. note:: According to the |DBAPI|_, the exception raised for a cursor out @@ -310,6 +307,13 @@ The ``cursor`` class except (ProgrammingError, IndexError), exc: deal_with_it(exc) + The method can be used both for client-side cursors and + :ref:`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