#13906: REPEATABLE READ (as used by default on MySQL) breaks atleast
QuerySet.get_or_create().
-------------------------------------+-------------------------------------
Reporter: | Owner:
sebastian_noack | Status: new
Type: | Component: Database layer
Cleanup/optimization | (models, ORM)
Milestone: 1.4 | Severity: Normal
Version: SVN | Keywords: mysql transaction
Resolution: | isolation
Triage Stage: Accepted | Has patch: 1
Needs documentation: 1 | Needs tests: 0
Patch needs improvement: 1 | Easy pickings: 0
UI/UX: 0 |
-------------------------------------+-------------------------------------
Comment (by jsdalton):
Note: I just submitted a patch for the issue Karen reported with regards
to `SelectForUpdateTests.test_block()` in #16490. That issue was better
solved (in my opinion) by committing the transaction in the test to get a
fresh read rather than waiting on a larger decision on REPEATABLE READ vs.
READ COMMITTED. So that particular issue doesn't really have much of a
bearing on this discussion after all. `get_or_create()` is really the only
place where there is an issue.
--
Ticket URL: <https://code.djangoproject.com/ticket/13906#comment:24>
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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en.
