#30441: Persistent connections not reused on request.
-------------------------------------+-------------------------------------
Reporter: cryptogun | Owner: nobody
Type: Bug | Status: new
Component: Database layer | Version: master
(models, ORM) |
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Mahdi Zareie):
Replying to [comment:3 Mahdi Zareie]:
> correct me if I'm wrong, `CONN_MAX_AGE` is a numeric parameter, and None
is not a valid value for a numeric parameter. isn't it reasonable to raise
ImproperlyConfigured exception when someone set this parameter to None?
I just understood what's going on, according to the documentations:
> The default value is 0, preserving the historical behavior of closing
the database connection at the end of each request. To enable persistent
connections, set CONN_MAX_AGE to a positive number of seconds. For
unlimited persistent connections, set it to None.
--
Ticket URL: <https://code.djangoproject.com/ticket/30441#comment:4>
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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/067.d77138020da5b68a78b55d7650a234f4%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
