+1 from me. Here's a patch to add autocommit to MySQL: https://github.com/django/django/pull/857
FWIW: any sort of scheme where a transaction is kept open all request (including a transaction that only ever reads), will cause you serious pain if you're trying to do migrations on MySQL with traffic. Alex On Fri, Mar 1, 2013 at 7:07 AM, Carl Meyer <c...@oddbird.net> wrote: > On 03/01/2013 05:48 AM, Aymeric Augustin wrote: > > Basically, Django intends to provide autocommit by default. Rather than > > fight the database adapter that itselfs fights the database, I propose > > to simply turn autocommit on, and stop implicitly starting and > > committing transactions. Explicit is better than implicit. > > +1. > > Carl > > -- > 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 django-developers+unsubscr...@googlegroups.com. > To post to this group, send email to django-developers@googlegroups.com. > Visit this group at http://groups.google.com/group/django-developers?hl=en > . > For more options, visit https://groups.google.com/groups/opt_out. > > > -- "I disapprove of what you say, but I will defend to the death your right to say it." -- Evelyn Beatrice Hall (summarizing Voltaire) "The people's good is the highest law." -- Cicero -- 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 django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. Visit this group at http://groups.google.com/group/django-developers?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
