On Tue, 8 May 2018 at 22:12 Simon Slavin <slav...@bigfraud.org> wrote:
> On 8 May 2018, at 10:56am, R Smith <ryansmit...@gmail.com> wrote:
> > Thank you for clarifying - but it is still my understanding that the DB
> is not locked (if only in WAL mode), so the backup API, even with -1,
> either must ignore changes, or restart. My proposed flag is to lock rather
> than restart or ignore.
> You can lock the database yourself, using BEGIN EXCLUSIVE or BEGIN
> IMMEDIATE depending on which you want. Then do all the backup stuff, then
> COMMIT or ROLLBACK without having changed anything.
Having just tested that (for alternate purposes), it doesn't work. The
sqlite3_backup_step calls following a "BEGIN IMMEDIATE" instruction
sqlite-users mailing list