On 30 May 2015, at 9:41pm, Samuel Tebeka <samtebeka at gmail.com> wrote:
> This is the official doc:
>
> 1. Process A starts a read transaction on the database and does one or
> more SELECT statement. Process A keeps the transaction open.
> 2. Process B updates the database, changing values previous read by
> process A.
> 3. Process A now tries to write to the database. But process A's view
> of the database content is now obsolete because process B has modified the
> database file after process A read from it. Hence process B gets an
> SQLITE_BUSY_SNAPSHOT error.
>
> Do you have a recommendation about how to resolve this issue?
Around the commands which read and write to the database, try executing
BEGIN EXCLUSIVE
the command
END
This should mean that the errors go away but it might slow down your programs
unacceptably. Please tell us what happens.
Simon.
