MySQL transaction isolation level decorator

Nope. According to the docs:

"Internally, Django keeps a stack of states. Activations and deactivations must be balanced.

For example, commit_on_success() switches to managed mode when entering the block of code it controls; when exiting the block, it commits or rollbacks, and switches back to auto mode.

So commit_on_success() really has two effects: it changes the transaction state and it defines a transaction block. Nesting will give the expected results in terms of transaction state, but not in terms of transaction semantics. Most often, the inner block will commit, breaking the atomicity of the outer block."

https://docs.djangoproject.com/en/dev/topics/db/transactions/#transaction-states