> 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 thought that the name of this undo implementation was Muhammad Aqeel. Its PgVolvra, which is arguably a worse name- phonetically.
Can’t unsee PgVulva
PgMulva
Let's call it Muhammad Aqeel then.
Honestly a better name
I'd imagine you could actually build this reusing a lot of the existing WAL code if you were Inclined
You might not even have the WAL from long ago.
I see this as an easier way to create a log table.
This is really cool.
My org uses log tables and triggers and I wish that databases would offer something like this in a declarative manner.
Friendly reminder that database software is the literal last thing you want to entrust to vibe coders.