#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: 0 | Needs tests: 0
Patch needs improvement: 0 | Easy pickings: 0
-------------------------------------+-------------------------------------
Changes (by graham_king):
* milestone: => 1.4
Comment:
I changed the url in the patch to link to this ticket, instead of directly
to Sebastien's blog.
Do you think the attached patch is the right way to go? If so, the ticket
is Accepted, and it only adds a comment, so is it time for attention from
a core developer? I'm tentatively adding Milestone 1.4.
I have been bitten by REPEATABLE READ when using Django's ORM from a long-
running worker (the type of thing that listens on a message queue), so I'm
a strong +1 here.
@adamnelson You mean you can run the ./runtests.py test suite on MySQL /
InnoDB? You don't get an error importing the fixture in aggregation? This
is probably off-topic, so could you mail me directly: gra...@gkgk.org
--
Ticket URL: <http://code.djangoproject.com/ticket/13906#comment:15>
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.
