#34202: Strict time zone name condition in PostgreSQL DatabaseWrapper.
-------------------------------------+-------------------------------------
Reporter: Alexander Ebral | Owner: nobody
Type: | Status: closed
Cleanup/optimization |
Component: Database layer | Version: 4.1
(models, ORM) |
Severity: Normal | Resolution: wontfix
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 Mariusz Felisiak):
* status: new => closed
* type: Bug => Cleanup/optimization
* resolution: => wontfix
Comment:
Maintaining list of time zone aliases in Django is not doable. Also, `UTC`
and `Etc/UTC` are not considered equal by `zoneinfo`:
{{{
>>> import zoneinfo
>>> z1 = zoneinfo.ZoneInfo("UTC")
>>> z2 = zoneinfo.ZoneInfo("Etc/UTC")
>>> z1 == z2
False
}}}
so I don't think there is much we can do in Django itself. I'd recommend
to use `UTC` in PostgreSQL or `Etc/UTC` in `settings.TIME_ZONE`.
--
Ticket URL: <https://code.djangoproject.com/ticket/34202#comment:2>
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/01070184f00a4409-3d264692-b2c0-4080-b7d3-f4211ef6e107-000000%40eu-central-1.amazonses.com.
