Hi Shai and list, I tested your patch with my applications. All my unittests pass.
Shai Berger wrote: > Hi list, > > #9964 is about managed transactions not being committed under transaction > middleware (or transaction.commit_on_success decorator) after the database > was > modified via raw SQL. The root cause of that is that, today, managed > transactions only become "dirty" when there is clear evidence of database > change -- that is, when a known-to-change-the-database operation (such as > saving a model) is performed. If this isn't the case (as in the case of raw > SQL), the user is required to call transaction.set_dirty() to get correct > behavior. > ... -- Thomas Guettler, http://www.thomas-guettler.de/ E-Mail: guettli (*) thomas-guettler + de -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-develop...@googlegroups.com. To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
