Re: [sqlite] Another unexpected source of SQLITE_BUSY_SNAPSHOT

2016-09-18 Thread Florian Weimer
* Dan Kennedy: >> My concern is about sqlite3_step(UPDATE) without a following >> sqlite3_reset(UPDATE). Perhaps I should change my wrapper to >> unconditionally call sqlite3_reset() after DML-related sqlite3_step(), >> whether the stepping operation succeeded or not. > > For a DML statement, I u

[sqlite] Another unexpected source of SQLITE_BUSY_SNAPSHOT

2015-11-11 Thread Dan Kennedy
On 11/11/2015 01:19 AM, Florian Weimer wrote: > * Dan Kennedy: > >> On 10/18/2015 10:27 PM, Florian Weimer wrote: >>> My first surprise was SQLITE_BUSY_SNAPSHOT from BEGIN IMMEDIATE (see >>> ?SQLITE_BUSY_SNAPSHOT from BEGIN IMMEDIATE?). I have found another >>> source of such snapshot failures wit

[sqlite] Another unexpected source of SQLITE_BUSY_SNAPSHOT

2015-11-10 Thread Florian Weimer
* Dan Kennedy: > On 10/18/2015 10:27 PM, Florian Weimer wrote: >> My first surprise was SQLITE_BUSY_SNAPSHOT from BEGIN IMMEDIATE (see >> ?SQLITE_BUSY_SNAPSHOT from BEGIN IMMEDIATE?). I have found another >> source of such snapshot failures with WAL-mode databases. >> >> I like to pre-compile my

[sqlite] Another unexpected source of SQLITE_BUSY_SNAPSHOT

2015-10-19 Thread Dan Kennedy
On 10/18/2015 10:27 PM, Florian Weimer wrote: > My first surprise was SQLITE_BUSY_SNAPSHOT from BEGIN IMMEDIATE (see > ?SQLITE_BUSY_SNAPSHOT from BEGIN IMMEDIATE?). I have found another > source of such snapshot failures with WAL-mode databases. > > I like to pre-compile my DML statements before

[sqlite] Another unexpected source of SQLITE_BUSY_SNAPSHOT

2015-10-18 Thread Florian Weimer
My first surprise was SQLITE_BUSY_SNAPSHOT from BEGIN IMMEDIATE (see ?SQLITE_BUSY_SNAPSHOT from BEGIN IMMEDIATE?). I have found another source of such snapshot failures with WAL-mode databases. I like to pre-compile my DML statements before starting transactions, mainly for the implied syntax che