#30398: Check database connection's health before its reused
-------------------------------------+-------------------------------------
Reporter: Przemysław Suliga | Owner:
| Przemysław Suliga
Type: New feature | Status: assigned
Component: Database layer | Version: master
(models, ORM) |
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 1
Needs tests: 1 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Ran Benita):
Taking a risk of detracting the discussion a bit, but given Djagno's async
future, wouldn't this be the time to revisit the decision to use
persistent connections over a connection pool? For most async frameworks
(we use gevent, but will be the same with ASGI), persistent connections
don't work since async tasks are not reused like threads/processes,
instead a task is spawned per request.
--
Ticket URL: <https://code.djangoproject.com/ticket/30398#comment:6>
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/065.f43e9173f5dc90aa556834fe0814eaf2%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
