Hi Everyone, I was wondering if a Django guru was able to verify if my mental model of how django transactions operate is correct.
The situation that I have is that I'd like to place the transaction.commit_on_success decorator around a custom function on my model. At the same time, I would also like to enable the TransactionMiddleware for my views. The former would protect the database from invalid states while using the shell while the latter would protect the database if a view function happens to raise an exception. The part where I am particularly concerned is what will happen if a view function calls a model function with the commit_on_success decorator set. If the model function executes correctly but the view function fails, will the database roll back to the state before the view function started - or will the changes performed by the model function persist. My thinking (and looking at the django source) is that transaction state is being managed as a stack and therefore you can enter a managed block N times and until you also leave transaction management N times, nothing at all will be committed. So in the above situation, everything will be fine and the database will be in the state as if the view never happened. I'd just like some confirmation if what I am thinking is correct or if I am horribly confused and am tackling the issue incorrectly. Thanks B -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-us...@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
