Re: [sqlite] WAL journal mode & sqlite3_backup_step()

2017-02-15 Thread Olivier Mascia
> Le 15 févr. 2017 à 18:44, Clemens Ladisch a écrit : > > Olivier Mascia wrote: >> A good approach ... is to drive the backup by a single call to >> sqlite3_backup_step() > > This is indeed what you should do with WAL. > >> The only downside is that I loose the capability

Re: [sqlite] WAL journal mode & sqlite3_backup_step()

2017-02-15 Thread Clemens Ladisch
Olivier Mascia wrote: > A good approach ... is to drive the backup by a single call to > sqlite3_backup_step() This is indeed what you should do with WAL. > The only downside is that I loose the capability to monitor (or inform users > if needed) of the backup progress. That was never the

Re: [sqlite] WAL journal mode & sqlite3_backup_step()

2017-02-15 Thread Olivier Mascia
> Le 15 févr. 2017 à 17:41, Olivier Mascia a écrit : > >> Le 15 févr. 2017 à 16:04, Olivier Mascia a écrit : >> >> Dear all, >> >> https://www.sqlite.org/c3ref/backup_finish.html#sqlite3backupstep makes it >> clear that connections (other than the one used

Re: [sqlite] WAL journal mode & sqlite3_backup_step()

2017-02-15 Thread Olivier Mascia
> Le 15 févr. 2017 à 16:04, Olivier Mascia a écrit : > > Dear all, > > https://www.sqlite.org/c3ref/backup_finish.html#sqlite3backupstep makes it > clear that connections (other than the one used for the backup feature) which > writes in between calls to

[sqlite] WAL journal mode & sqlite3_backup_step()

2017-02-15 Thread Olivier Mascia
Dear all, https://www.sqlite.org/c3ref/backup_finish.html#sqlite3backupstep makes it clear that connections (other than the one used for the backup feature) which writes in between calls to sqlite3_backup_step() will force the next sqlite3_backup_step() to start again the whole copy