4 ms·
> At least at some points we need proper transactional behaviour and Sqlite implements that by talking a temporary copy of the database - not an option for larg
by xucheng 7y ago
> At least at some points we need proper transactional behaviour and Sqlite implements that by talking a temporary copy of the database - not an option for large keyrings.
I don’t understand how GPG maintainers think they can implement something better (function and performance-wise) than a proper database engine. Also I don’t think GPG will ever need to handle keyring lager than 140TB [1].
[1]: https://www.sqlite.org/whentouse.html https://www.sqlite.org/whentouse.html
- mikeash 7y agoI’m pretty sure SQLite doesn’t implement transactions that way anyway. That’s a pretty bad misunderstanding of how it works. I suppose it’s easy to think you can do better than SQLite if you think SQLite is really bad.
- blattimwind 7y agoSQLite never implemented transactions that way, neither in undo nor WAL mode. Someone might have misunderstood how undo logging / rollback journals work. Only pages to be changed are recorded in the rollback journal, not the entire database.