Good 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

Good 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