#24810: Reopen database connection automatically when no transaction is active
-------------------------------------+-------------------------------------
Reporter: Aymeric Augustin | Owner: nobody
Type: Uncategorized | Status: new
Component: Database layer | Version: dev
(models, ORM) |
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 1 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Johannes Maron):
* type: New feature => Uncategorized
Comment:
I can second this issues. We see this happening thousands of times, but
still at random (we have a lot of traffic). We have a relatively small
stack, and I scanned it completely to see if we have any place that closes
the connection prematurely. This is not the case. Therefore, I would
contest the ticket status and would propose to move this to bug.
This is certainly unexpected for a framework that comes with a very
sophisticated ORM and is probably not debuggable or mitigable event for
most experienced developers.
--
Ticket URL: <https://code.djangoproject.com/ticket/24810#comment:14>
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 view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/0107017f9861d94d-8af1d38a-f5b5-48bc-9a93-424048dde830-000000%40eu-central-1.amazonses.com.
