From f26bdcbc6c9c4c74a63f12e3e0250473ce3c3f3d Mon Sep 17 00:00:00 2001 From: Daniele Varrazzo Date: Fri, 12 Feb 2021 11:08:55 +0100 Subject: [PATCH] Fix server-side cursors docs typos Reported by @lelit, thank you! --- docs/connection.rst | 2 +- docs/cursor.rst | 4 ++-- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/connection.rst b/docs/connection.rst index 04a7842a7..74bfcfd33 100644 --- a/docs/connection.rst +++ b/docs/connection.rst @@ -59,7 +59,7 @@ The `!Connection` class .. automethod:: cursor Calling the method without a *name* creates a client-side cursor, - specifying a *name* crates a server-side cursor. See + specifying a *name* creates a server-side cursor. See :ref:`cursor-types` for the details. .. note:: You can use :ref:`with conn.cursor(): ...` diff --git a/docs/cursor.rst b/docs/cursor.rst index 89d8e0159..18ecbf25f 100644 --- a/docs/cursor.rst +++ b/docs/cursor.rst @@ -202,7 +202,7 @@ The `!ServerCursor` class not. if `!None` leave the choice to the server. :type scrollable: `!Optional[bool]` :param hold: if `!True` allow the cursor to be used after the - transaction cretaing it has committed. + transaction creating it has committed. :type hold: `!bool` Create a server cursor with given `name` and the *query* in argument. @@ -242,7 +242,7 @@ The `!ServerCursor` class .. automethod:: scroll - These method uses the MOVE_ SQL statement to move the current position + This method uses the MOVE_ SQL statement to move the current position in the server-side cursor, which will affect following `!fetch*()` operations. If you need to scroll backwards you should probably use `scrollable=True` in `execute()`. -- 2.47.2