#13906: REPEATABLE READ (as used by default on MySQL) breaks atleast
QuerySet.get_or_create().
---------------------------------------------------+------------------------
Reporter: sebastian_noack | Owner: nobody
Status: new | Milestone:
Component: Database layer (models, ORM) | Version: 1.2
Resolution: | Keywords:
Stage: Unreviewed | Has_patch: 0
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
---------------------------------------------------+------------------------
Comment (by sebastian_noack):
The solution I have proposed includes adding a setting, but would make
READ COMMITTED the default. Yes, this would break backward compatibility.
But the user just have to set a setting, to get the old behaviour back.
And on the other hand it makes most ORM code even more compatible with
MySQL. So code that was tested against any other database backends would
work more reliable on MySQL with that change.
Btw, I have looked at modeltests/transactions/models.py and noted that the
tests in there are bypassed for mysql. I don't have looked in detail at
the tests, but it looks like that there are known issues with MySQL and
transactions. And I would not wonder if that is because of the different
isolation level.
--
Ticket URL: <http://code.djangoproject.com/ticket/13906#comment:5>
Django <http://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 [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en.
