#13906: REPEATABLE READ (as used by default on MySQL) breaks atleast
QuerySet.get_or_create().
-------------------------------------+-------------------------------------
Reporter: Sebastian Noack | Owner: (none)
Type: | Status: closed
Cleanup/optimization |
Component: Database layer | Version: master
(models, ORM) |
Severity: Normal | Resolution: wontfix
Keywords: mysql transaction | Triage Stage: Accepted
isolation |
Has patch: 1 | Needs documentation: 1
Needs tests: 0 | Patch needs improvement: 1
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 `get_or_create()` still doesn't work correctly
(and probably can't?) under repeatable read.
--
Ticket URL: <https://code.djangoproject.com/ticket/13906#comment:40>
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/073.d08ca6e814ea8febd803e52cb0e3d475%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
