On 19 sept. 2013, at 23:38, Anssi Kääriäinen <anssi.kaariai...@thl.fi> wrote:
> Here, another_obj.save() will succeed. But the transaction will be *always* > rolled back, silently. I don't see any good reason not to error out when > using a connection which is going to be rolled back in always. As far as I can tell that's the actual proposal in your email, and I'm OK with trying to to raise exceptions when making a query and get_rollback returns True. I'm not sure it's doable; patch welcome ;-) -- Aymeric. -- 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. For more options, visit https://groups.google.com/groups/opt_out.
