#28794: tx_isolation deprecation warning with MySQL 5.7.20+
-------------------------------------+-------------------------------------
Reporter: JC | Owner: Sergey
Type: | Fedoseev
Cleanup/optimization | Status: closed
Component: Database layer | Version: 2.0
(models, ORM) |
Severity: Normal | Resolution: fixed
Keywords: mysql | 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 David Wasylciw):
Replying to [comment:8 Tim Graham]:
> It doesn't qualify for a backport per our
[https://docs.djangoproject.com/en/dev/internals/release-process
/#supported-versions supported versions policy]. 1.11 only receives
security and data loss fixes.
Fair enough! Was just hoping that a patch would be a better way of
supressing the constant depreciation warnings, wish the MySQL backend had
the same silent depreciation warnings as everything else now has.
--
Ticket URL: <https://code.djangoproject.com/ticket/28794#comment:9>
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/067.aeefef89219be92be73cf6488593b84a%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
