#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: | postgresql, connection, closed
Unreviewed | Has patch: 0
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 0 |
-------------------------------------+-------------------------------------
Changes (by Alex):
* needs_docs: => 0
* needs_tests: => 0
* needs_better_patch: => 0
Comment:
Well it should really only do this in the case that the InterfaceError is
a "connection already closed" one, I remember seeing Mike Bayer bitching
that there was no programmatic way to do it, so perhaps we should steal
the hack he ended up using from him.
--
Ticket URL: <http://code.djangoproject.com/ticket/15802#comment:1>
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.
