I'm not sure this is so cut and dry. For two reasons: 1) If a project has a lot of databases configured, created and ending a transaction in all of them for every request/response cycle could get expensive, and following that:
2) This is enough of a change in behavior that it shouldn't just be fixed in the existing middleware without some kind of control over it. Maybe some flag in settings as to which databases the transaction middleware affects, with the default database being the default? -- You received this message because you are subscribed to the Google Groups "Django developers" group. To view this discussion on the web visit https://groups.google.com/d/msg/django-developers/-/AIhK86iYu1YJ. To post to this group, send email to django-developers@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.
