On Wednesday, August 5, 2015 at 3:59:39 PM UTC+2, Marcin Nowak wrote: > > <snip> > I must try to do replacement or bring old behaviour of commit_manually() > with my custom wrapper. I'm trying to change code as less as possible. >
To be honest the "issues" you outlined here seem to suggest a bigger problem within your own code. I am aware that it is really hard and annoying to change from old style transactions to the new ones in big projects, but given the fact that atomic() just works and I have yet to see a project which used old style transactions properly (see Aymerics presentation on transactions), I think it is worth it. > You're asking what could be done better.. Generally speaking - an API > compatibility layer. As a maintainer of big and old project I would like to > import "commit_manually" from special module delivered with Django, which > will guarantee stability and compatibility. > And defer upgrading to a proper transaction management for another few years? Seriously, if your project is to big to upgrade stick with 1.4 and use a distribution which provides LTS support for it (but yes, ultimately you will have to switch, but from what I hear Redhat is going to support 1.4 for another while :D)=… Cheers, Florian -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" 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. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/ade4b6f6-14e2-412e-bd42-ad725df96bf2%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
