#21670: New Model.save() mechanism causes deadlocks in mysql transactions
-------------------------------------+-------------------------------------
Reporter: err | Owner: nobody
Type: Bug | Status: closed
Component: Database layer | Version: 1.6
(models, ORM) |
Severity: Normal | Resolution: wontfix
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Tim Graham):
* status: new => closed
* resolution: => wontfix
Comment:
In Django 2.0, the MySQL backend will default to read committed (#27683).
I think we can close this ticket in light of that. The resolution is
"wontfix" in the sense that there's still a problem under repeatable read.
If my analysis is incorrect, please reopen with more details as I'm not a
MySQL user.
--
Ticket URL: <https://code.djangoproject.com/ticket/21670#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 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/061.cd37d8793dd356db2a959c38df7d932c%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
