Home > Object Persistency API > API Reference > Nested Transactions
As described in the previous chapter there is a begin method within the TXContext interface that allows for creating nested transactions.
Database interactions are always executed in the context of a transaction, i.e. main transactions are automatically started. Therefore the begin method has the sole purpose of starting a nested transaction. A subsequent call to commit or rollback will not commit or rollback the main transaction but only the nested transaction.
Hence you can rollback to certain savepoints within your transactional context. Please note that you can start a nested transaction within a nested transaction as well.
Here's a simple example that shows the interaction with the TXContext interface when using nested transactions.
- insert - create an object; the main transaction has been automatically started.
- begin - start nested transaction 1.
- insert - create an object.
- begin - started nested transaction 2.
- update - change an object.
- rollback - rollback nested transaction 2.
- commit - commit nested transaction 1.
- update - update an object.
- commit - commit the main transaction.
- ...
Next chapter: Events