Re: [sqlite] SQLITE_ERROR instead of SQLITE_BUSY or clarification of busy state errors

2019-10-31 Thread mailing lists
Hi, what I do not really understand is why the statement in step (3) is allowed to read the database at all and not aborts by a SQLITE_BUSY error. The transaction in step (2) is modifying the database, in my case the statement is creating the database. But assume that step (2) is modifying it

Re: [sqlite] SQLITE_ERROR instead of SQLITE_BUSY or clarification of busy state errors

2019-10-30 Thread Keith Medcalf
On Wednesday, 30 October, 2019 16:33, mailing lists wrote: >I face the following issue: >1) SQLite has been compiled with SQLITE_THREADSAFE=1 and >SQLITE_DEFAULT_SYNCHRONOUS=3 >2) I am opening in a thread a new database (standard journal mode) and >creating some tables, indices etc. (explicit

Re: [sqlite] SQLITE_ERROR instead of SQLITE_BUSY or clarification of busy state errors

2019-10-30 Thread Simon Slavin
On 30 Oct 2019, at 10:33pm, mailing lists wrote: > In this second thread (step (3)) I get an SQLITE_ERROR in sqlite3_prepare. I > actually expected an SQLITE_BUSY error. Remark: as step (2) is a transaction > no tables exist when step (3) starts execution. > > Is my understanding correct that

[sqlite] SQLITE_ERROR instead of SQLITE_BUSY or clarification of busy state errors

2019-10-30 Thread mailing lists
Hi, I face the following issue: 1) SQLite has been compiled with SQLITE_THREADSAFE=1 and SQLITE_DEFAULT_SYNCHRONOUS=3 2) I am opening in a thread a new database (standard journal mode) and creating some tables, indices etc. (explicit transaction) 3) while creating the database a new database