News for hackers. Stuff that matters.
Re:Why SQLite succeeded as a database (2016) by hinkley on Wednesday February 19, 2020 @11:32PM (#22372690)
I had a different interpretation. It's not uncommon in commercial code to use a sort of copy-on-write behavior where every edit creates a new row and marks the other one as dead (for instance, filling in or blanking out a column to mark it defunct). You leave an audit trail behind.

Which, with a little bit of work, can be used to revert to earlier versions.

There are no comments on this comment yet.