5 ms·
A ledger should be a database with only select and insert privileges. eg. No update or delete queries should be allowed.
by z3t4 7y ago
A ledger should be a database with only select and insert privileges. eg. No update or delete queries should be allowed.
- p1necone 7y agoIf you're writing a ledger for your own personal record keeping, and not for some third party to be able to audit you wouldn't it be helpful to be able to keep history tidy and clean up mistakes without having to add extra entries?
- repiret 7y agoYes in the sense that data shouldn't be destroyed, but you still need to be able to correct mistakes - those corrections just need to leave an audit trail.
- dmos62 7y agoThat's a solved problem: git.
- tty2300 7y agoGit allows rewriting history though.
- dmos62 7y agoBut not by mistake, and it facilitates remote backups. I took this to be the problem parent was talking about.
- jolmg 7y agoIf you're sharing the repo, then you'll have to convince everyone to discard their copy of the original history and accept your modified version. And if that's done and everyone accepts the new history, the original can still be kept in each copy of the repo on another branch and the rewrite seen in the reflog. If commits are being signed, you can keep undeniable record of who contributed what in the original history, and who rewrote it. If the point is to forbid you to modify even when you're the only person working on it, any common database will allow you to update and delete when you enter with administrative privileges, so I don't see the difference.
- deleted 7y ago[deleted]