Transactions are not really nested, as the underlying support in the db drivers varies so much from one db to the other that it would be impossible to get it acceptably reliable across implementations.
What happens is that the outer transaction gets committed at the end, the inner ones do not.
Also if any of the inner transactions gets rolled back (ie. $db->rollback(); ), the complete transaction stack gets rolled back.
Principal Consultant International Business
Member of the Community Project Board
<i>Transactions are not really nested...</i> Yes, I did expect that, but it seemed to describe best what appears to happen (or rather what the code looks like) ;)
<i>What happens is that the outer transaction gets committed at the end, the inner ones do not. Also if any of the inner transactions gets rolled back (ie. $db->rollback(); ), the complete transaction stack gets rolled back.</i> Is that a standard MySQL behavior, or some eZ mechanism supporting it? Couldn't find MySQL manual analyzing such scenario...
