#15802: Django stops functioning when the database (PostgreSQL) closes the
connection
-------------------------------------+-------------------------------------
Reporter: | Owner: nobody
Rick.van.Hattem@… | Status: new
Type: Bug | Component: Database layer
Milestone: | (models, ORM)
Version: 1.3 | Severity: Normal
Resolution: | Keywords: database, postgres,
Triage Stage: Accepted | postgresql, connection, closed
Needs documentation: 0 | Has patch: 0
Patch needs improvement: 0 | Needs tests: 0
-------------------------------------+-------------------------------------
Comment (by anonymous):
Although it would be cleaner to only do this in case of an `connection
already closed` `InterfaceError`. I can't really think of a valid reason
to keep `self.connection` after trying to close it.
Either it succeeded or failed, but the odds are that the connection is not
usable anymore in either case. It shouldn't be much of a problem since the
exception is re-raised anyway.
But a clean solution (catching this specific error silently) would be
preferred indeed.
--
Ticket URL: <http://code.djangoproject.com/ticket/15802#comment:4>
Django <http://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en.
