#35240: Django doesn't set Postgres timezone to UTC when using psycopg3
-------------------------------+--------------------------------------
Reporter: Fabi | Owner: nobody
Type: Bug | Status: closed
Component: Uncategorized | Version: 4.2
Severity: Normal | Resolution: needsinfo
Keywords: | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------+--------------------------------------
Comment (by Fabi):
`DATABASES` does not have a `TIME_ZONE` set.
While there might be other bugs in this specific code, I was able to fix
this specific problem by defaulting the database to UTC.
I'll leave it up to you if you want to close this or leave it open for
further investigation.
--
Ticket URL: <https://code.djangoproject.com/ticket/35240#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 django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/0107018dc8a7b7f4-d64e689e-b1ec-40ea-a99a-16c596c0dc8a-000000%40eu-central-1.amazonses.com.
