#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
UI/UX: 0 | Easy pickings: 0
-------------------------------------+-------------------------------------
Changes (by mtredinnick):
* ui_ux: => 0
* easy: => 0
Comment:
That SQLAlchemy code looks fragile in the medium-term. I tend to agree
with comment 4: we make a decent attempt to close the connection and then
call it "closed" anyway. Before committing something along those lines,
can anybody think of a case where that is going to bite us (I can't)?
--
Ticket URL: <https://code.djangoproject.com/ticket/15802#comment:5>
Django <https://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 [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en.
