How do you handle situation in which exception is raised from view,
TransactionMiddleware rolls back the open transaction, but subsequently 
SessionMiddleware updates session in database with broken data
(i.e. something that points to what was rolled back 
by TransactionMiddleware) ?

This is an edge case but quite interesting one, at least for me.

-- 
Tomasz Zielinski
pyconsultant.eu

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/django-users?hl=en.

Reply via email to