Hi Christian,
On 18/04/2006, at 8:22, Christian Smith wrote:
SQLite will make possible whatever is safe. Just be prepared to handle
SQLITE_BUSY and SQLite will take care of the rest.
Great. This is what I do now. No worries here then...
If the indexing process uses a large SQLite cache (using the
cache_size
PRAGMA) then the indexer can perform some of the indexing without
promoting the lock to EXCLUSIVE, and allow concurrent access with
readers.
This is using a RESERVED lock. However, the EXCLUSIVE lock will be
required once the cache is filled with dirty pages as pages will be
required to be spilled to the database file (and hence the rollback
journal etc will be created.) This will occur once all current
readers
have finished. When an EXCLUSIVE lock is required, no new readers are
allowed.
Thanks so much for the clarification.
Regards,
-- Tito
