#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
-------------------------------------+-------------------------------------
Changes (by Mariusz Felisiak):
* cc: Aymeric Augustin (added)
Comment:
Replying to [comment:2 Josh Smeaton]:
> Thank you!
>
> I think the docs are ambiguous. It sounds like the configured time zone
will be used for the connection from the docs I linked, but in practice
the connection uses UTC unless a query is executed on the session? Or is
there another connection parameter that controls the session timezone?
>
> Might be worth a docs update to clarify the current behaviour?
Doc clarifications are always welcome. I hope that Aymeric will chime in
;)
--
Ticket URL: <https://code.djangoproject.com/ticket/35267#comment:3>
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/0107018e097bf056-287cd82c-f522-4c32-99fc-6d18e55a47cf-000000%40eu-central-1.amazonses.com.
