[sqlite] Dealing with SQLITE_BUSY

I use sqlite3_open() to open two connections, and I have configured journal_mode=WAL, threadsafe=2. Connection 1 is doing: sqlite3_exec(db1, "BEGIN", 0, 0, ); sqlite3_exec(db1, "SELECT * FROM t1;", 0, 0, ); sqlite3_exec(db1, "INSERT INTO t1 VALUES(1, 1, \"aa\”)”, 0, 0, ); //SQLITE_BUSY

Re: [sqlite] Using Sqlite nuget package in a .Net test assembly

Greg Pagendam-Turner wrote: > > Using Sqlite nugget package version 3.13 > Are you using the full (desktop) .NET Framework? If so, the NuGet package you probably want is probably "System.Data.SQLite". -- Joe Mistachkin ___ sqlite-users mailing list

Re: [sqlite] Dealing with SQLITE_BUSY

Nick wrote: > I use sqlite3_open() to open two connections, and I have configured > journal_mode=WAL, threadsafe=2. > > Connection 1 is doing: > sqlite3_exec(db1, "BEGIN", 0, 0, ); > sqlite3_exec(db1, "SELECT * FROM t1;", 0, 0, ); > sqlite3_exec(db1, "INSERT INTO t1 VALUES(1, 1, \"aa\”)”, 0, 0, );

Re: [sqlite] Improper error message

Not quite as original as yours, but SQLite version 3.22.0 2018-01-22 18:45:57 Enter ".help" for usage hints. Connected to a transient in-memory database. Use ".open FILENAME" to reopen on a persistent database. sqlite> attach database 'distinct.sqlite' as "distinct"; sqlite> create table

Re: [sqlite] Dealing with SQLITE_BUSY

On Thu, 22 Feb 2018 14:36:07 +, Simon Slavin wrote: > On 22 Feb 2018, at 11:24am, Clemens Ladisch wrote: > >> Use "BEGIN IMMEDIATE" instead to tell the DB that you intend to write. > > Depending on how you want your locks to work, BEGIN EXCLUSIVE

Re: [sqlite] Dealing with SQLITE_BUSY

On 2/22/2018 5:54 AM, Nick wrote: I use sqlite3_open() to open two connections, and I have configured journal_mode=WAL, threadsafe=2. Connection 1 is doing: sqlite3_exec(db1, "BEGIN", 0, 0, ); sqlite3_exec(db1, "SELECT * FROM t1;", 0, 0, ); sqlite3_exec(db1, "INSERT INTO t1 VALUES(1, 1,

Re: [sqlite] Dealing with SQLITE_BUSY

Yes. See https://sqlite.org/lang_transaction.html From that page: "Transactions can be deferred, immediate, or exclusive. The default transaction behavior is deferred. Deferred means that no locks are acquired on the database until the database is first accessed. Thus with a deferred

Re: [sqlite] Dealing with SQLITE_BUSY

On 22 Feb 2018, at 11:24am, Clemens Ladisch wrote: > Use "BEGIN IMMEDIATE" instead to tell the DB that you intend to write. Depending on how you want your locks to work, BEGIN EXCLUSIVE may work better. Do remember when setting your timeout, that you have to set it in