Shevek wrote: > Why would I have a transaction of non-zero size on a read-only connection?
What do you mean with "size"? A read-only transaction still puts a shared lock on the database file. A read-only transaction will not change the DB file, but SQLite has lots of internal data structures in memory, and those can change. To give each thread its own data structures, use separate connections. > I assume db->mutex is preventing concurrency "db" is the connection object; each one has its own mutex. Regards, Clemens _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
