I have a DB operation that will take a few minutes (computing a leaderboard) so it needs to be done in a background thread (with its own connection). I was hoping to do this:
1. read various fields from table A as inputs to the leaderboard calculation 2. in a thread, compute leaderboard and write to table B (which main thread doesn't write to). In other words, the main thread only writes to table A and the background thread only writes to table B. I was hoping that miscellaneous concurrent writes to table A would not give me SQLITE_BUSY, since the background thread is only writing to table B. But I get the impression the entire DB is locked - is that correct? My code will be simpler if I don't ever have to deal with SQLITE_BUSY. Cheers Tom -- View this message in context: http://sqlite.1065341.n5.nabble.com/Does-SQLite-lock-the-entire-DB-for-writes-or-lock-by-table-tp76921.html Sent from the SQLite mailing list archive at Nabble.com. _______________________________________________ sqlite-users mailing list [email protected] http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
