> I think "single writer, multiple readers" is the simplest way to describe
sqlite's approach to isolation

I’m not sure if this summarization paints enough of a picture about how SQLite 
restricts interleaving of read & write operations between concurrent 
transactions, to guarantee isolation. For eg, in Rollback journal, a writing 
transaction looking to commit blocks other readers (as you mentioned), but WAL 
does not.
_______________________________________________
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users

Reply via email to