The transaction_guard class has not turned out to have many use cases in the public API: most operations don't need it, or can be performed idempotently. As such, it should be removed from the public API to simplify things.
However, its initial implementation still serves a purpose as a RAII type for nestable SQLite transactions, and so it can be retained as an internal utility.
The
transaction_guardclass has not turned out to have many use cases in the public API: most operations don't need it, or can be performed idempotently. As such, it should be removed from the public API to simplify things.However, its initial implementation still serves a purpose as a RAII type for nestable SQLite transactions, and so it can be retained as an internal utility.