4 ms·
Make sure to also run a test with multiple threads concurrently interacting with SQLite. Due to SQLite's exclusive locking mechanism, this causes actual issues
by kuschku 9y ago
Make sure to also run a test with multiple threads concurrently interacting with SQLite.
Due to SQLite's exclusive locking mechanism, this causes actual issues with concurrent writes and reads.
- jamiesonbecker 9y agoGood point - but reads never blocked except during a (concurrent) write, which wouldn't likely be much of a problem with the presumably read-heavy autocomplete scenario described here. Incidentally, even that's not even an issue anymore, if you enable SQLite's write-ahead logging support: https://www.sqlite.org/wal.html https://www.sqlite.org/wal.html