#15802: Django stops functioning when the database (PostgreSQL) closes the
connection
-------------------------------------+-------------------------------------
Reporter: Rick.van.Hattem@… | Owner: aaugustin
Type: | Status: closed
Cleanup/optimization |
Component: Database layer | Version: 1.6
(models, ORM) |
Severity: Normal | Resolution: fixed
Keywords: database, postgres, | Triage Stage: Accepted
postgresql, connection, closed |
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 1
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by aaugustin):
* status: assigned => closed
* resolution: => fixed
Comment:
Replying to [comment:31 aaugustin]:
> I'm reopening this ticket because I want to think about reopening the
connection automatically when no transaction is in progress.
Since this ticket was getting long and confusing, I've opened another
ticket for this improvement: #24810.
--
Ticket URL: <https://code.djangoproject.com/ticket/15802#comment:40>
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 unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/081.6934d7b30f7b46b63b4d3ca77cc47c3e%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
