On 1 mars 2013, at 14:38, Javier Guerra Giraldez <[email protected]> wrote:
> On Fri, Mar 1, 2013 at 7:48 AM, Aymeric Augustin > <[email protected]> wrote: >> To alleviate the pain, Django commits after each ORM write. > > just curious: why is it so? i can't think of any reason not to tie > transaction to the request/response cycle by default. (ie what > TransactionMiddleware does). TransactionMiddleware makes efficient connection pooling nearly impossible. > this is the default on a few other frameworks i use, and has already > saved my behinds more than once. I agree that it's a good default for small-to-medium sites. This is somewhere in a later part of my plan :) -- 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.
