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 processing.
What about databases set for journal_mode=WAL? Is backup_step() also restarting the whole procedure after any write commit happen? Or only if some checkpointing occurs? Said differently, is the whole scheme of sqlite3_backup_* API meant to build a copy of the database, including whatever would be in the WAL journal, or is the goal to get a copy of what is seen by the implicit read transaction of the connection doing the backup? -- 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
