> Le 15 févr. 2017 à 18:44, Clemens Ladisch <clem...@ladisch.de> 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 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).
Indeed, the reporting was probably not the primary motivation for the stepping, anyway reporting progress was obviously considered by authors: sqlite3_backup_remaining() is useless except between steps. :) Thanks, -- Best Regards, Meilleures salutations, Met vriendelijke groeten, Olivier Mascia, http://integral.software _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
