SQLite has a very well defined and documented set of abstractions about what can and can’t go wrong on the layers of abstraction it relies on. “Out of two writes, at least one will be successful” is not part of that, and doesn’t make sense to me.
Second-guessing the storage layer like that will never be able to catch all problems with it (e.g. drives or file systems lying about the durability of write commands).
Sorry but bit errors happen all the time at scale, and most commonly in controllers. SQLite is used in so many environments for its robustness rather than actually for SQL. Seems odd to argue agsinst it actually
Drives, controllers, and file systems lying about write durability is another great reason to add more robustness, good point
SQLite has a very well defined and documented set of abstractions about what can and can’t go wrong on the layers of abstraction it relies on. “Out of two writes, at least one will be successful” is not part of that, and doesn’t make sense to me.
Second-guessing the storage layer like that will never be able to catch all problems with it (e.g. drives or file systems lying about the durability of write commands).