On 1 Jun 2015, at 7:05am, Dan Kennedy <danielk1977 at gmail.com> wrote:
> On 05/31/2015 04:11 AM, Simon Slavin wrote: >> On 30 May 2015, at 9:59pm, Samuel Tebeka <samtebeka at gmail.com> wrote: >> >>> I'm doing a BEGIN EXCLUSIVE before every write statement already, should I >>> do it for read steatements as well? >> It's worth a try. I'm not sure what's wrong here, I'm just hoping we find a >> way to change what's happening enough to figure out a good solution. > > SQLITE_BUSY_SNAPSHOT indicates that a connection is trying to upgrade a > read-transaction to read/write, but that the database has been modified since > the read transaction was opened and it is not possible to do so. That's why I recommended BEGIN EXCLUSIVE, guessing that nothing could stop an exclusive lock being upgraded. But I might be wrong. Simon.
