On Fri, Mar 1, 2013 at 4:11 PM, Alex Gaynor <alex.gay...@gmail.com> wrote: > 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.
Wouldn't the transaction be opened when you make modifications, and closed once the reqeust returns? Ie, in a typical read situation: No transaction. In the typical write situation, the transaction is started somewhere in the view, and closed once an HTTP redirect is returned? I do agree that 99.9% of the sites committing on the end of the request is the right thing to do, and do think that this should be the default, although I realize that debate is already lost. //Lennart -- 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.
