summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorKunal Marwaha <marwahaha@berkeley.edu>2019-06-11 00:29:23 -0700
committerDaniele Varrazzo <daniele.varrazzo@gmail.com>2019-06-19 00:32:54 +0100
commitc32dbf357c39e03d5ef0ca23b36b1466739448df (patch)
tree3cf5900dfdfa9aeb6fcada37e8c9bb438777fa3f
parentbc65c636aef14ccdb89f8abec1f28a677c1ff0b4 (diff)
downloadpsycopg2-c32dbf357c39e03d5ef0ca23b36b1466739448df.tar.gz
typo: remove 'a'
-rw-r--r--doc/src/faq.rst2
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/src/faq.rst b/doc/src/faq.rst
index 926b05e..aab537b 100644
--- a/doc/src/faq.rst
+++ b/doc/src/faq.rst
@@ -271,7 +271,7 @@ When should I save and re-use a connection as opposed to creating a new one as n
What are the advantages or disadvantages of using named cursors?
The only disadvantages is that they use up resources on the server and
- that there is a little overhead because a at least two queries (one to
+ that there is a little overhead because at least two queries (one to
create the cursor and one to fetch the initial result set) are issued to
the backend. The advantage is that data is fetched one chunk at a time:
using small `~cursor.fetchmany()` values it is possible to use very