#33037: TruncDay error when using offset timezones on MySQL
-------------------------------------+-------------------------------------
Reporter: Alan | Owner: nobody
Type: Bug | Status: closed
Component: Database layer | Version: dev
(models, ORM) |
Severity: Normal | Resolution: invalid
Keywords: mysql truncdate | Triage Stage:
timezone | Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Mariusz Felisiak):
* resolution: duplicate => invalid
Comment:
`+3` and `-3` (after fixing #32992) both works for me on MySQL. Your issue
is probably caused by [https://docs.djangoproject.com/en/3.2/ref/databases
/#time-zone-definitions an empty time zone table in the MySQL database]
(see also a [https://docs.djangoproject.com/en/3.2/ref/models/querysets
/#database-time-zone-definitions warning]).
--
Ticket URL: <https://code.djangoproject.com/ticket/33037#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 django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/069.0d6ce794120e80f723bd2a8b4ad382e1%40djangoproject.com.
