#30786: MySQL backend's has_zoneinfo_database check requires read access to
mysql.time_zone
-------------------------------------+-------------------------------------
Reporter: Andrew Williams | Owner: Andrew
| Williams
Type: Bug | Status: closed
Component: Database layer | Version: 3.0
(models, ORM) |
Severity: Normal | Resolution: fixed
Keywords: | Triage Stage: Ready for
| checkin
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Mariusz Felisiak <felisiak.mariusz@…>):
In [changeset:"def1857d9b7c79a48c0c3ecf997321fa76b479d9" def1857d]:
{{{
#!CommitTicketReference repository=""
revision="def1857d9b7c79a48c0c3ecf997321fa76b479d9"
[3.0.x] Fixed #30786 -- Used CONVERT_TZ to check if the time zone
definitions are installed on MySQL.
Replaced a timezone check in the MySQL backend with one that doesn't
require access to the mysql.time_zone database.
Backport of 3346b78a8a872286a245d1e77ef4718fc5e6be1a from master
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/30786#comment:6>
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/066.1684ff8bd08be37439d3c06f28278681%40djangoproject.com.
