Opened 12 years ago

Closed 12 years ago

#19507 closed Bug (duplicate)

django.db doesn't wrap / replace psycopg2.InterfaceError

Reported by: Antoine Pitrou Owned by: nobody
Component: Database layer (models, ORM) Version: 1.4
Severity: Normal Keywords:
Cc: Triage Stage: Accepted
Has patch: no Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: no UI/UX: no

Description

django.db currently only wraps the backend's DatabaseError and IntegrityError. However, psycopg2 can raise a "psycopg2.InterfaceError: connection already closed" when trying to run a query more than once against an unavailable (e.g. stopped) database. This means catching django.db.DatabaseError isn't enough to catch all possible runtime errors (other than programming errors).

It would be nice if Django also replaced psycopg2's InterfaceError with a generic Django exception.

(note: slightly related with issue #15802)

Change History (4)

comment:1 by Ramiro Morales, 12 years ago

See also #15901.

comment:2 by Aymeric Augustin, 12 years ago

Triage Stage: UnreviewedAccepted

comment:3 by Anssi Kääriäinen, 12 years ago

Type: UncategorizedBug

comment:4 by Aymeric Augustin, 12 years ago

Resolution: duplicate
Status: newclosed

Closing as a duplicate of #15901.

Note: See TracTickets for help on using tickets.
Back to Top