Re: [sqlite] Undo logs and transactions

Yes, I completely agree. But a single "undoable event" generates multiple changes to the database (which might as well be done inside a single transaction). Thus one click on Undo results in multiple changes to undo the event (ie, undoing the entire event's transaction). This implies that

Re: [sqlite] Undo logs and transactions

True, but even an application would need to "undo" in transactions, I'd think. Like, if a user drags a widget from column A to B, it generates an INSERT in one column and a DELETE in another. Pressing Undo once would leave it in both columns, which is probably unexpected. Anyway, I was more

Re: [sqlite] Undo logs and transactions

the Undo/Redo mechanism described is not really for transactions but rather a "Button" within an application. So that the user can undo/redo changes. Only one transaction can be active at a time. So to the best of my knowledge there is no "transaction number" as there can be only 1. Now you may