Re: ATOMIC_REQUESTS Middleware inside Transaction

2015-08-20 Thread Tim Graham
I'm not sure what type of reply or answer you are looking for. Overhauling Django middleware as discussed on the developers mailing list might be best in the long run. https://groups.google.com/d/topic/django-developers/uW5Ogio8QBc/discussion On Thursday, August 20, 2015 at 3:54:20 AM UTC-4,

Re: ATOMIC_REQUESTS Middleware inside Transaction

2015-08-20 Thread guettli
Sad, not reply since nine days ... Is there something you don't understand? Please ask :-) Am Dienstag, 11. August 2015 09:24:37 UTC+2 schrieb guettli: > > I am not happy that settings.ATOMIC_REQUESTS=True isolates only the view, > but not the middlewares > in one transaction. > > For

ATOMIC_REQUESTS Middleware inside Transaction

2015-08-11 Thread guettli
I am not happy that settings.ATOMIC_REQUESTS=True isolates only the view, but not the middlewares in one transaction. For applications like reversion (app which records the changes of a model) it is very important, that the middleware runs inside the same transaction. If storing the changes