#36964: Documentation incorrectly states that persistent connections don't work
with runserver
-------------------------------------+-------------------------------------
Reporter: Adam Sołtysik | Owner: Shubh Rai
Type: | Status: assigned
Cleanup/optimization |
Component: Documentation | Version: 5.2
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 1
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Shubh Rai):
* stage: Unreviewed => Accepted
Comment:
A pull request has been opened for this documentation clarification:
https://github.com/django/django/pull/20827
The PR updates the wording about persistent connections when using the
development server to clarify that they may still be observed when
`CONN_MAX_AGE` is enabled, but their behavior may not reflect production
environments due to autoreload and the thread-per-request model.
--
Ticket URL: <https://code.djangoproject.com/ticket/36964#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 view this discussion visit
https://groups.google.com/d/msgid/django-updates/0107019cb79864eb-b8202d7d-7dd0-497a-aa2a-0c366404556d-000000%40eu-central-1.amazonses.com.
