#35016: Missing documentation for setting libpq options with the PostgreSQL
backend
--------------------------------------+------------------------------------
Reporter: Roman Donchenko | Owner: nobody
Type: Cleanup/optimization | Status: new
Component: Documentation | Version: 5.0
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
--------------------------------------+------------------------------------
Changes (by Mariusz Felisiak):
* type: Uncategorized => Cleanup/optimization
* stage: Unreviewed => Accepted
Comment:
This vary depending on your database backend (as
[https://docs.djangoproject.com/en/dev/ref/settings/#std-setting-OPTIONS
documented]), but I agree that it's worth mentioning that the PostgreSQL
backend passes the content of OPTIONS as keyword arguments to the
connection constructor, allowing for more advanced control of driver
behavior.
Would you like to prepare a patch?
--
Ticket URL: <https://code.djangoproject.com/ticket/35016#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 view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/0107018c3d80e3a4-0e72dd91-6a64-447f-918d-2e2d78eb45e5-000000%40eu-central-1.amazonses.com.
