#34659: mysql backend creates queries using CONVERT_TZ even when this is not
supported
-------------------------------------+-------------------------------------
Reporter: Klaas van Schelven | Owner: nobody
Type: Uncategorized | Status: closed
Component: Database layer | Version: 4.2
(models, ORM) |
Severity: Normal | Resolution: duplicate
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
* resolution: => duplicate
* component: Uncategorized => Database layer (models, ORM)
Comment:
Duplicate of e.g. #33075.
When `USE_TZ` is `True`, fields are converted to the current time zone
before filtering (see
[https://docs.djangoproject.com/en/stable/ref/models/querysets/#date
__date docs]). This requires
[https://docs.djangoproject.com/en/stable/ref/models/querysets/#database-
time-zone-definitions time zone definitions in the database] as documented
(in both places).
--
Ticket URL: <https://code.djangoproject.com/ticket/34659#comment:7>
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/01070188c50c97ac-a937b790-5e04-4d51-b328-48179142c555-000000%40eu-central-1.amazonses.com.
