On 5 mars 2013, at 12:50, Shai Berger <[email protected]> wrote: > At least the "delete duplicates" example I've pointed to shows, that it's > quite easy to write code that is correct now, under the defaults, with MySql > and will break with the change.
http://stackoverflow.com/questions/8965391/delete-duplicate-rows-in-django-db In fact this code is already unsafe under MySQL with "repeatable read"; you need "serializable" to make it safe. The current behavior doesn't map to any common programming idiom and doesn't make much sense in general. The only explanation I've found is "we had to commit after making changes otherwise they weren't saved". As a consequence, code written "unwittingly" is more likely to be incorrect than correct. -- 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.
