#23318: Management command dbshell does not use DATABASE[...]['OPTIONS'] to set
env
PGOPTIONS
-------------------------------------+-------------------------------------
Reporter: benjaoming | Owner: Flavio
| Curella
Type: New feature | Status: assigned
Component: Core (Management | Version: master
commands) |
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 1
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by felixxm):
Replying to [comment:7 Dulmandakh]:
> .... may be used to set many connection configurations of psycopg2 other
than **options** or PGOPTIONS.
I'm not sure what does it mean? You want to pass `options` to the
`PGOPTIONS` so how it can support sth else? The list of all available
options can be found in [https://www.postgresql.org/docs/10/runtime-
config.html the PostgreSQL docs]. Also I'm not sure
([https://github.com/django/django/pull/3168#issuecomment-55174417 as
pointed by Tim]) if passing all possible options is safe.
--
Ticket URL: <https://code.djangoproject.com/ticket/23318#comment:8>
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/068.bd96a30ea82ceeb60600ed5c8f5648ea%40djangoproject.com.
