#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:
| Unreviewed
Has patch: 1 | Needs documentation: 1
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Shubh Rai):
* needs_docs: 0 => 1
Comment:
I have opened a pull request addressing this documentation clarification.
PR: https://github.com/django/django/pull/20827
Ticket: #36964
The change clarifies the wording about persistent database connections
when using the development server. In practice, persistent connections can
still be observed when CONN_MAX_AGE is enabled, but due to the development
server’s thread-per-request model and autoreload behavior, connection
reuse may be inconsistent and not representative of production
environments.
Feedback and suggestions are welcome.
--
Ticket URL: <https://code.djangoproject.com/ticket/36964#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 view this discussion visit
https://groups.google.com/d/msgid/django-updates/0107019cb7948224-0e41cadd-4569-4b89-a85c-29ab1a5af9c8-000000%40eu-central-1.amazonses.com.
