2010-02-26 03:17:52 +03:00
|
|
|
`psycopg2.errorcodes` -- Error codes defined by PostgreSQL
|
2010-02-13 08:25:21 +03:00
|
|
|
===============================================================
|
|
|
|
|
|
|
|
.. sectionauthor:: Daniele Varrazzo <daniele.varrazzo@gmail.com>
|
|
|
|
|
2010-02-16 00:59:49 +03:00
|
|
|
.. index::
|
|
|
|
single: Error; Codes
|
|
|
|
|
2010-02-13 08:25:21 +03:00
|
|
|
.. module:: psycopg2.errorcodes
|
|
|
|
|
2010-02-16 00:59:49 +03:00
|
|
|
.. testsetup:: *
|
|
|
|
|
|
|
|
from psycopg2 import errorcodes
|
|
|
|
|
2010-02-13 08:25:21 +03:00
|
|
|
.. versionadded:: 2.0.6
|
|
|
|
|
2010-02-16 00:59:49 +03:00
|
|
|
This module contains symbolic names for all PostgreSQL error codes and error
|
2010-02-26 03:17:52 +03:00
|
|
|
classes codes. Subclasses of `~psycopg2.Error` make the PostgreSQL error
|
|
|
|
code available in the `~psycopg2.Error.pgcode` attribute.
|
2010-02-13 08:25:21 +03:00
|
|
|
|
|
|
|
From PostgreSQL documentation:
|
|
|
|
|
|
|
|
All messages emitted by the PostgreSQL server are assigned five-character
|
|
|
|
error codes that follow the SQL standard's conventions for :sql:`SQLSTATE`
|
|
|
|
codes. Applications that need to know which error condition has occurred
|
|
|
|
should usually test the error code, rather than looking at the textual
|
|
|
|
error message. The error codes are less likely to change across
|
|
|
|
PostgreSQL releases, and also are not subject to change due to
|
|
|
|
localization of error messages. Note that some, but not all, of the error
|
|
|
|
codes produced by PostgreSQL are defined by the SQL standard; some
|
|
|
|
additional error codes for conditions not defined by the standard have
|
|
|
|
been invented or borrowed from other databases.
|
|
|
|
|
|
|
|
According to the standard, the first two characters of an error code
|
|
|
|
denote a class of errors, while the last three characters indicate a
|
|
|
|
specific condition within that class. Thus, an application that does not
|
|
|
|
recognize the specific error code can still be able to infer what to do
|
|
|
|
from the error class.
|
|
|
|
|
|
|
|
.. seealso:: `PostgreSQL Error Codes table`__
|
|
|
|
|
2012-02-28 20:28:07 +04:00
|
|
|
.. __: http://www.postgresql.org/docs/current/static/errcodes-appendix.html#ERRCODES-TABLE
|
2010-02-13 08:25:21 +03:00
|
|
|
|
|
|
|
|
2010-02-16 00:59:49 +03:00
|
|
|
An example of the available constants defined in the module:
|
|
|
|
|
|
|
|
>>> errorcodes.CLASS_SYNTAX_ERROR_OR_ACCESS_RULE_VIOLATION
|
|
|
|
'42'
|
|
|
|
>>> errorcodes.UNDEFINED_TABLE
|
|
|
|
'42P01'
|
|
|
|
|
2014-07-31 16:13:27 +04:00
|
|
|
Constants representing all the error values defined by PostgreSQL versions
|
2014-08-25 01:04:43 +04:00
|
|
|
between 8.1 and 9.4 are included in the module.
|
2010-02-16 00:59:49 +03:00
|
|
|
|
|
|
|
|
|
|
|
.. autofunction:: lookup(code)
|
|
|
|
|
|
|
|
.. doctest::
|
|
|
|
|
|
|
|
>>> try:
|
|
|
|
... cur.execute("SELECT ouch FROM aargh;")
|
|
|
|
... except Exception, e:
|
|
|
|
... pass
|
|
|
|
...
|
|
|
|
>>> errorcodes.lookup(e.pgcode[:2])
|
|
|
|
'CLASS_SYNTAX_ERROR_OR_ACCESS_RULE_VIOLATION'
|
|
|
|
>>> errorcodes.lookup(e.pgcode)
|
|
|
|
'UNDEFINED_TABLE'
|
|
|
|
|
|
|
|
.. versionadded:: 2.0.14
|
2010-02-13 08:25:21 +03:00
|
|
|
|
|
|
|
|
2010-04-20 02:51:42 +04:00
|
|
|
.. testcode::
|
|
|
|
:hide:
|
|
|
|
|
|
|
|
conn.rollback()
|