#35267: DateTimeField does not seem to be translated back to the local timezone
on
data retrieval on Postgres
-------------------------------------+-------------------------------------
Reporter: Josh Smeaton | Owner: nobody
Type: Uncategorized | Status: new
Component: Database layer | Version: 5.0
(models, ORM) |
Severity: Normal | Resolution:
Keywords: orm datetimefield | Triage Stage:
timezones | Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Natalia Bidart):
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.
Amazing, thank you for letting us know. Do you think the first docs you
read still need adjustment? I'm thinking that the `TIME_ZONE` setting link
in the paragraph would be better pointed to this instead:
https://docs.djangoproject.com/en/dev/ref/settings/#time-zone
--
Ticket URL: <https://code.djangoproject.com/ticket/35267#comment:5>
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/0107018e0c276cb4-68fe7528-7ed0-42ba-addd-682744eb1e48-000000%40eu-central-1.amazonses.com.
