> pgVolvra records every row change on the tables you choose. For each change, it keeps the row as it was, and the row as it became, along with who made the change, when, and in which transaction. When something goes wrong, it uses that record to put the affected rows back, and it touches nothing else.
You've essentially replicated the WAL s functionality
I'd imagine you could actually build this reusing a lot of the existing WAL code if you were Inclined
I'd imagine you could actually build this reusing a lot of the existing WAL code if you were Inclined
My org uses log tables and triggers and I wish that databases would offer something like this in a declarative manner.