#34202: Strict time zone name condition in PostgreSQL DatabaseWrapper.
-------------------------------------+-------------------------------------
Reporter: Alexander Ebral | Owner: nobody
Type: Bug | Status: new
Component: Database layer | Version: 4.1
(models, ORM) |
Severity: Normal | Resolution:
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 Mariusz Felisiak):
> Maybe we need to change this condition to some fuzzy form? Something
like this?:
>
> {{{
> conn_timezone_name not in timezone_name and timezone_name not in
conn_timezone_name
> }}}
This would be really clunky, e.g. all `UTC+X` timezone would be consider
equal to `UTC`.
--
Ticket URL: <https://code.djangoproject.com/ticket/34202#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 view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/01070184eddd5ce5-6c88f0f4-1bb3-40af-9632-804f1622f343-000000%40eu-central-1.amazonses.com.
