On Wed, Mar 6, 2013 at 4:15 AM, Jeremy Dunck <[email protected]> wrote: > I, for one, would prefer that we not recommend TransactionMiddleware > so highly.
then what would be the recommended option to have transactions tied to the request/response cycle? probably @commit_on_success for every view that modifies the database? i could live with that... still, the "set and forget" nature of TransactionMiddleware is very attractive. -- Javier -- 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.
