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 primary purpose of having multiple steps; it was intended to allow concurrent read and write accesses (before WAL existed). And the progress would look silly when it actually restarts ... Regards, Clemens _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
