#30398: Check database connection's health before its reused
-------------------------------------+-------------------------------------
Reporter: Przemysław Suliga | Owner: nobody
Type: New feature | Status: new
Component: Database layer | Version: master
(models, ORM) |
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Carlton Gibson):
* stage: Unreviewed => Accepted
Comment:
OK, yes, this seems reasonable to at least look at. (Assuming there's no
massive performance hit or such...)
Aside: once of the main benefits of a move to async is that it allows easy
creation of background tasks, for which this kind of health check might be
suitable. (Not celery's model, but related...)
--
Ticket URL: <https://code.djangoproject.com/ticket/30398#comment:1>
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.ed78e74dd0efc0a3495be7b62d698b6e%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
