#30150: Django 1.11 with MySQL 8: "Unknown system variable 'TX_ISOLATION'"
-------------------------------------+-------------------------------------
Reporter: Carsten Fuchs | Owner: nobody
Type: Bug | Status: closed
Component: Database layer | Version: 1.11
(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
-------------------------------------+-------------------------------------
Comment (by Carsten Fuchs):
Replying to [comment:4 Adam (Chainz) Johnson]:
> Carsten, you can always create a subclassed database backend in your
project to add the compatibility with MySQL 8 in Django 1.11. You might
find it's not just transaction_isolation that's the relevant change, maybe
there are more things to backport from 2.0 for that.
Yes, there are certainly a lot more considerations involved with using
MySQL 8 with Django 1.11, e.g. #18392 and #29451.
Fortunately, during the tests and research that I spent during the last
weeks, I have not become aware of any other issues that indicate anything
but a reliable running of MySQL 8 with Django 1.11.
Given Django 1.11's status as noted by Tim above and given that I intend
to upgrade to Django 2.0+ as soon as I got confident that my transition
from Oracle to MySQL went well, there is no point in adding features to
1.11 that won't make it into an official release. (And unfortunately, I
don't think that I understand enough of the Django source code to address
issues at that level, at least at the scale of a database backend.)
--
Ticket URL: <https://code.djangoproject.com/ticket/30150#comment:5>
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 post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/066.2f7d5d1cb29d270159e0b4c4aa3fc3f5%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
