At the moment, Daobab supports transaction for DataBaseTarget only. Transactions over in in-memory or remote targets are not implemented yet.
Transaction is necessary for any operation changing the target content.
It’s required for every insert, update and delete.
However, there are some circumstances, where opening transaction for read operations might be a good thing.
First of all, for most cases, you don't have to bother with transactions at all.
In case of simple insert, update or delete, executing an execute() method, open and close transaction in the background.
However, if you want to wrap more operations, you would like to have control over the transaction related process.
Daobab provides solutions for
- automatic transactions
- wrap many operations into single transaction
- manually open, commit and rollback transaction
- transaction propagations