On 5 mars 2013, at 01:50, Shai Berger <[email protected]> wrote: > I want to point out how ironic this whole issue turns out.
That's a storm in a teapot. Let's keep some perspective: - People using MyISAM aren't affected. - People using the transaction middleware aren't affected. - People using commit_on_success aren't affected. In addition to the above, to end up with data corruption, you must: - be aware that MySQL runs on "repeatable read" by default, - have checked that Django doesn't set another isolation level — this isn't documented, - be aware of Django's default transactional behavior — virtually no one understands the first paragraph of the transaction docs, - have chosen to rely on this behavior to implicitly guarantee some integrity between a read and a subsequent write, - upgrade to Django 1.6 without taking into account the release notes or without understanding their consequences for you, - be running a medium- or high-traffic website where race conditions are likely, - have code that fails silently rather than raise an error on integrity violations. That's technically possible, but sufficiently unlikely to be acceptable as a _documented_ backwards incompatibility. -- Aymeric. -- You received this message because you are subscribed to the Google Groups "Django developers" 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]. Visit this group at http://groups.google.com/group/django-developers?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
