This is the 2nd major issue I can recall caused by MySQL default of REPEATABLE READ transaction isolation level. I think Django should simply switch itself to a default of using READ COMMITTED, consistent with (all?) other supported database backends, and document how, if a user really really wants to use REPEATABLE READ, they can do so (I assume Django could allow that?), and what known problems when using basic Django functions they may run into if they do so.
I fear our existing approach of documenting how certain functions don't work by default on MySQL (e.g. get_or_create) is not really helping the majority of our users. I believe switching instead to making Django code itself work by default on MySQL would be a better long-term solution for those who use MySQL with Django, and avoid future cases like this one that has been discovered (years after we knew get_or_create was broken by default transaction isolation level on MySQL). On Mon, Mar 14, 2016 at 11:15 AM, Tim Graham <timogra...@gmail.com> wrote: > Could some MySQL users take a look at ticket #26347 [0] and recommend how > to proceed? I think it's probably not a new issue but I'm a bit surprised > it hasn't come up before if so. > > [0] https://code.djangoproject.com/ticket/26347 > > -- > You received this message because you are subscribed to the Google Groups > "Django developers (Contributions to Django itself)" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to django-developers+unsubscr...@googlegroups.com. > To post to this group, send email to django-developers@googlegroups.com. > Visit this group at https://groups.google.com/group/django-developers. > To view this discussion on the web visit > https://groups.google.com/d/msgid/django-developers/286b0efb-673f-42d7-a1f3-5de76fc039c5%40googlegroups.com > <https://groups.google.com/d/msgid/django-developers/286b0efb-673f-42d7-a1f3-5de76fc039c5%40googlegroups.com?utm_medium=email&utm_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. Visit this group at https://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/CACS9rae4U0e80-h%3DesTXFUi%3DLxWQ-XiMAp%3DAdkXcR0FnJVT2Cg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
