#35016: Missing documentation for setting libpq options with the PostgreSQL
backend
-----------------------------------------+------------------------
Reporter: SpecLad | Owner: nobody
Type: Uncategorized | Status: new
Component: Documentation | Version: 5.0
Severity: Normal | Keywords:
Triage Stage: Unreviewed | Has patch: 0
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 0 | Easy pickings: 0
UI/UX: 0 |
-----------------------------------------+------------------------
As far as I can see, when a database uses the
`django.db.backends.postgresql` engine, any options from the `OPTIONS` key
that are not recognized by the engine itself are passed directly to the
underlying libpq library. This way you can set options like
[https://www.postgresql.org/docs/current/libpq-connect.html#LIBPQ-CONNECT-
SSLMODE `sslmode`].
But this doesn't seem to actually be documented anywhere, so it's unclear
whether this is actually a supported feature or just an implementation
artifact.
If this really is supported, then it should be documented - presumably in
[https://docs.djangoproject.com/en/5.0/ref/databases/#postgresql-notes
PostgreSQL notes].
--
Ticket URL: <https://code.djangoproject.com/ticket/35016>
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/0107018c3adab798-3965d76b-c3d3-4c62-b876-8e70f2dc7e20-000000%40eu-central-1.amazonses.com.
