3 ms·
These all sounds like load-specific / ancillary concerns. I don't think most people are in one of those cases, and most people will greatly benefit from WAL. W
by masklinn 2y ago
These all sounds like load-specific / ancillary concerns.
I don't think most people are in one of those cases, and most people will greatly benefit from WAL. WAL should absolutely be the default unless you have a good reason to not use it.
- chasil 2y agoYou may prefer non-acid characteristics in your databases in general. I do not. There may be specific uses, but standards should be followed when possible.
- giraffe_lady 2y ago"When possible" in this case being simply don't enable the WAL if your use requires transactions across multiple attached sqlite DBs.
- masklinn 2y ago> You may prefer non-acid characteristics in your databases in general. No. Quite the opposite. However the multi-database case strikes me as a very limited edge case, I would be surprised if double digit % users of sqlite even knew it’s an option let alone used it, and the concern is further lessened because afaik things like FKs do not work cross-db.
- pdimitar 2y agoACID guarantees work just fine. They don't work perfectly in scenarios where SQLite should not be used anyway: multiple machines accessing the same DB file over network, and having multiple attached databases. None of these use cases are common.
- deleted 2y ago[deleted]