#23524: Django postgres connection's timezone is always set to UTC. Breaks
date_trunc function
----------------------------------+--------------------------------------
Reporter: Mactory | Owner:
Type: Bug | Status: closed
Component: contrib.postgres | Version: 1.6
Severity: Normal | Resolution: invalid
Keywords: | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
----------------------------------+--------------------------------------
Changes (by aaugustin):
* status: new => closed
* needs_better_patch: => 0
* resolution: => invalid
* needs_tests: => 0
* needs_docs: => 0
Comment:
This is by design and it's
[https://docs.djangoproject.com/en/stable/ref/databases/#optimizing-
postgresql-s-configuration documented]. See also the discussions on
django-developers leading to the implementation of time zone support in
Django 1.4.
You may use `connection.ops.datetime_trunc_sql` (a private API), or look
at what it returns and reimplement it by yourself.
--
Ticket URL: <https://code.djangoproject.com/ticket/23524#comment:1>
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/065.683b6c8c74e560e13fd4b51115066b98%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
