On 1 maalis, 14:48, Aymeric Augustin <aymeric.augus...@polytechnique.org> wrote:
> Yay or nay? +1. I discussed this on IRC with Aymeric. I tried to find cases where this breaks currently working code, and I was mostly unsuccessful. It seems there could be such cases (doing raw SQL writes, commit at end, and no ORM writes, all this outside transaction management), but it seems such cases are rare, and worked more by luck than knowledge of how Django's tx management works. Explicit transactions for such cases would be good anyways. This will be a backwards incompatible change. The current behaviour is explicitly documented, and the new behaviour is clearly different in some cases. However, finding cases where one actually wants the current behaviour (ORM writes commit, raw SQL writes do not, and any query will start a transaction) is hard. Doing a full deprecation path for this will be ugly, so just changing this without deprecation period seems good to me. All in all, this might cause some pain to very small portion of users when upgrading to 1.6. Those users will almost certainly be happy after they have upgraded their code. Otherwise this will be a big win for everybody. - Anssi -- 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.
