#28625: DATABASES TIME_ZONE setting may be confused with TIME_ZONE
-------------------------------------+-------------------------------------
Reporter: Jon Ribbens | Owner: Jon
Type: | Ribbens
Cleanup/optimization | Status: assigned
Component: Documentation | Version: 1.11
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 1 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Tim Graham):
Why do you think "The same values are accepted as in the general TIME_ZONE
setting." didn't give a clue? Maybe it would be sufficient to add some
clarification to that sentence, e.g. This inner option of DATABASES
accepts the same values as the general TIME_ZONE setting."
Another option could be to prefix all the dictionary setting headers so it
appears as something like `DATABASES: TIME_ZONE`, but that would make the
table of contents less clean.
My goal is to find a solution that doesn't add too much extra verbosity
for someone reading the `DATABASES` setting docs from top to bottom
compared to someone skimming the docs.
--
Ticket URL: <https://code.djangoproject.com/ticket/28625#comment:6>
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/066.f8b7bce3c3f5609400439f7d7d1d400d%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
