Nick wrote: > On 11 Dec 2014, at 20:39, David King wrote: >> Why are you trying to hard to avoid using the backup API? It sounds >> like it does exactly what you want > > Backup API works great if you have periods of no writing. > However, if a process writes during the backup then the API would stop > and start over again. So if you have frequent writes then > theoretically the backup API would not complete.
The ".backup" command of the sqlite3 command-line shell uses a step size of 100 pages, i.e., gives other processes opportunities to write regularly. If you write your own backup tool that simply calls "sqlite3_backup_step(b, -1)", the entire database is copied in a single atomic transaction. Regards, Clemens _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
