Using SQLITE_OPEN_FULLMUTEX puts SQLite into serialized mode. This means that mutltiple threads can share a single connection but will block until the mutex is freed because the thread currently holding the mutex has left the SQLite code. Blocked threads will only experience a time delay (concurrency is reduced).
This is distinct from the SQLITE_LOCKED, which means that there is a (logical) conflict iin the same DB connection, e.g. attempting to drop a table in one thread while reading from the same table in another thread. -----Ursprüngliche Nachricht----- Von: sqlite-users [mailto:sqlite-users-boun...@mailinglists.sqlite.org] Im Auftrag von Prajeesh Prakash Gesendet: Mittwoch, 28. November 2018 08:33 An: SQLite mailing list <sqlite-users@mailinglists.sqlite.org> Betreff: [EXTERNAL] [sqlite] SQLITE_OPEN_FULLMUTEX Hi Members, I enabled the SQLITE_OPEN_FULLMUTEX in that case if one thread is trying to write in to the DB and other thread is trying to read from the DB (Same connection). In that case will it cause any SQLITE_LOCKED error. In some of the forum i found that if we enable the SQLITE_OPEN_FULLMUTEX the sqlite handle ( sqlite3 * handle) contains the mutex filed so when the sqlite library is invoking that API will wait for the mutex to get open. 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
