#35267: Correct TIME_ZONE setting reference in time zone topic.
-------------------------------------+-------------------------------------
Reporter: Josh Smeaton | Owner: Josh
Type: | Smeaton
Cleanup/optimization | Status: assigned
Component: Documentation | Version: 5.0
Severity: Normal | Resolution:
Keywords: orm datetimefield | Triage Stage: Accepted
timezones |
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 1 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Mariusz Felisiak):
* component: Database layer (models, ORM) => Documentation
* easy: 0 => 1
* owner: nobody => Josh Smeaton
* stage: Unreviewed => Accepted
* status: new => assigned
* summary:
DateTimeField does not seem to be translated back to the local
timezone on data retrieval on Postgres
=> Correct TIME_ZONE setting reference in time zone topic.
* type: Uncategorized => Cleanup/optimization
Comment:
Replying to [comment:4 Josh Smeaton]:
> The database connection settings have their own TIME_ZONE setting:
https://docs.djangoproject.com/en/5.0/ref/settings/#time-zone, which is
what the previous docs I was referring to must have been referencing:
https://docs.djangoproject.com/en/4.2/topics/i18n/timezones/#postgresql
>
> It makes sense to me now.
Thanks Josh. Assigned to you, I hope you don't mind fixing it ;)
--
Ticket URL: <https://code.djangoproject.com/ticket/35267#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 django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/0107018e0cd819e9-3f5e16b4-9e6c-4eeb-a668-fc65400648aa-000000%40eu-central-1.amazonses.com.
