On 4/9/20 7:33 PM, Howard Chu wrote: [...]
Tracking the existence of transactions in a language binding is almost certainly a wrong thing to do, completely unnecessary.
MHO: Actually as you must either abort or commit any transaction, any long-running application would need to keep track of active transactions. Complex control flows may need such.
How does LMDB react if you try to abort a committed transaction, or trying to commit an aborted transaction (the other two cases should be idempontent, hopefully)? Such tings could happen easily if the application does not track the state of active transactions.
Thanks in advance,
-- Dorian Taylor Make things. Make sense. https://doriantaylor.com