blob: 3c3d3c43b3cd5f0d77c401bb56ac8dca8a034243 (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
|
The `!psycopg` module
=====================
Psycopg implements the `Python Database DB API 2.0 specification`__. As such
it also exposes the `module-level objects`__ required by the specifications.
.. __: https://www.python.org/dev/peps/pep-0249/
.. __: https://www.python.org/dev/peps/pep-0249/#module-interface
.. module:: psycopg
.. autofunction:: connect
This is an alias of the class method `Connection.connect`: see its
documentation for details.
If you need an asynchronous connection use `AsyncConnection.connect`
instead.
.. rubric:: Exceptions
The standard `DBAPI exceptions`__ are exposed both by the `!psycopg` module
and by the `psycopg.errors` module. The latter also exposes more specific
exceptions, mapping to the database error states (see
:ref:`sqlstate-exceptions`).
.. __: https://www.python.org/dev/peps/pep-0249/#exceptions
.. parsed-literal::
`!Exception`
\|__ `Warning`
\|__ `Error`
\|__ `InterfaceError`
\|__ `DatabaseError`
\|__ `DataError`
\|__ `OperationalError`
\|__ `IntegrityError`
\|__ `InternalError`
\|__ `ProgrammingError`
\|__ `NotSupportedError`
.. data:: adapters
The default adapters map establishing how Python and PostgreSQL types are
converted into each other.
This map is used as a template when new connections are created, using
`psycopg.connect()`. Its `~psycopg.adapt.AdaptersMap.types` attribute is a
`~psycopg.types.TypesRegistry` containing information about every
PostgreSQL builtin type, useful for adaptation customisation (see
:ref:`adaptation`)::
>>> psycopg.adapters.types["int4"]
<TypeInfo: int4 (oid: 23, array oid: 1007)>
:type: `~psycopg.adapt.AdaptersMap`
|