3 ms·
> Bad default #3: SQLITE_BUSY errors with concurrent writers This is a weird complaint to me. When I use SQLite, I always make sure there is a single writer t
by throwaway2037 3mo ago
> Bad default #3: SQLITE_BUSY errors with concurrent writers
This is a weird complaint to me. When I use SQLite, I always make sure there is a single writer thread. Any thread can submit a write request in a thread-safe queue. If you follow this pattern, you never need to worry about SQLITE_BUSY errors.
- mort96 3mo agoAnd your scripts for rare tasks you haven't gotten around to making a GUI for also go through that queue? And your manual interactions with the database to fix problems? Or do you just risk crashing the program when you do those things?