Using the `!ClientCursor` should ensure that psycopg will always use the
`simple query protocol`__ for querying. In most cases, the choice of the
-fronted/backend protocol used is transparent on PostgreSQL. However, in some
+frontend/backend protocol used is transparent on PostgreSQL. However, in some
case using the simple query protocol is mandatory. This is the case querying
the `PgBouncer admin console`__ for instance, which doesn't support the
extended query protocol.
.. autoclass:: Dumper(cls, context=None)
This class is a formal `~typing.Protocol`. A partial implementation of
- this protocol (implementing everything except the `dump()` metood) is
+ this protocol (implementing everything except the `dump()` method) is
available as `psycopg.adapt.Dumper`.
:param cls: The type that will be managed by this dumper.
.. class:: psycopg.Transaction.Status()
.. autoclass:: psycopg.AsyncTransaction.Status()
- .. note: `:members:` doeesn't seem to work currently. Nested class problem?
+ .. note: `:members:` doesn't seem to work currently. Nested class problem?
.. attribute:: NON_STARTED
* - :ref:`binary-installation` (recommended for most users)
- ``pip install psycopg[binary]``
- - Precompiled C extensions, packaged with client lbiraries.
+ - Precompiled C extensions, packaged with client libraries.
- 🐇 Fast
- ❌ No
- ❌ No
Current release
---------------
-Psyocpg 3.3.3 (unreleased)
+Psycopg 3.3.3 (unreleased)
^^^^^^^^^^^^^^^^^^^^^^^^^^
Retain `Error.pgconn` when raising a single exception for multiple connection