Locking (errors SQLITE_LOCKED and SQLITE_BUSY) are about **WHAT** you are doing to the DB. There can be at most 1 thread (same process or different process, it does not matter) with a write transaction on any DB file at any time. Typically, a transaction involves multiple calls to sqlite functions (sqlite3_prepare() to compile the statement, the first call to sqlite3_step() starts the transaction and calling sqlite3_reset() or sqlite3_finalize() ends the transaction).
FULLMUTEX has nothing to do with transactions. Using threads is about **HOW** you are doing things to the DB. FULLMUTEX is about making sure that your threads take turns when sharing a single connection (with a single transaction). -----Ursprüngliche Nachricht----- Von: sqlite-users [mailto:sqlite-users-boun...@mailinglists.sqlite.org] Im Auftrag von Prajeesh Prakash Gesendet: Donnerstag, 29. November 2018 12:37 An: sqlite-users@mailinglists.sqlite.org Betreff: [EXTERNAL] [sqlite] Getting SQLITE_LOCKED Hi Team, I am writing to a table 1 and reading from table 2 both operation are from different DB connection i am getting SQLITE_LOCKED and when i try to read and write the same table from different connection i am getting same error. (I know read and write are the incompatible at same time). Why this happening bu default sqlite will act on FULLMUTEXT. Thank You _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users ___________________________________________ Gunter Hick | Software Engineer | Scientific Games International GmbH | Klitschgasse 2-4, A-1130 Vienna | FN 157284 a, HG Wien, DVR: 0430013 | (O) +43 1 80100 - 0 May be privileged. May be confidential. Please delete if not the addressee. _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
