#24810: Reopen database connection automatically when no transaction is active
-------------------------------------+-------------------------------------
Reporter: aaugustin | Owner: nobody
Type: New feature | Status: new
Component: Database layer | Version: master
(models, ORM) |
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by noky):
It should be noted that in the case where a daemon is accessing the DB via
the ORM, if the db connection is closed for some reason (usually the db
server restarting), then ALL subsequent DB read queries FAIL. At that
point, the process can no longer perform any read query since the db
connection is closed. I'm not concerned with retrying statements that
failed during the time the db was down, but it does seem like a bug that
the ORM completely fails to reconnect AT ALL. The funny thing is: if and
only if the process happens to perform a DB write after the DB connection
gets closed, then the ORM will open a new connection.
--
Ticket URL: <https://code.djangoproject.com/ticket/24810#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 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/067.b4bb1cd9fd690e383aee9f873a7cf316%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
