#24777: Add support for statement_timeout
-------------------------------------+-------------------------------------
Reporter: jdufresne | Owner: nobody
Type: New feature | Status: new
Component: Database layer | Version: master
(models, ORM) |
Severity: Normal | Resolution:
Keywords: | Triage Stage:
| Unreviewed
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by aaugustin):
It's usually preferable to define such settings in the database server
configuration to avoid the overhead of an extra SQL query on each
connection. Did you consider this, and if so, how do you plan to address
it? (`SET TIME ZONE` works similarly and has been the subject of long
discussions about not making an extra SQL query when not needed.)
I see that your patch only deals with PostgreSQL. In order to maintain
feature-parity between database backends, this option should be added to
every backend where it can be implemented.
However, if you're focusing on PostgreSQL, perhaps a more useful
generalization would be to support setting arbitrary connection options. I
would prefer adding a generic mechanism for setting connection options
rather than a special case for one of them that you happen to find useful.
--
Ticket URL: <https://code.djangoproject.com/ticket/24777#comment:2>
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/067.3446ec386ee468139a8aea5564e312e4%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
