Hi Simo, > Do not start a transaction this way. > Because we still want to commit any changes that successfully apply we > never want to do a global cancel, and because of how transaction nesting > works that means we never cancel any "transaction" at the single modify > operation level.
Who says that? I think it's quite useful to only apply all operations! We should at least have a command line option to control this. And also have all ldb tools in sync with this behavior. Could you please revert that for now. Then we could readd this to all tools with an option. Where I don't care what default behavior we choose. metze > Let each operation start its own transaction so that the transaction is > properly canceled if any error is returned and half committed operations > (though plugins failing) are properly reverted on a per operation basis.
signature.asc
Description: OpenPGP digital signature
