On Sep 26, 2017, at 9:01 AM, Warren Young <war...@etr-usa.com> wrote:
> On Sep 26, 2017, at 7:10 AM, Lonnie Abelbeck <li...@lonnie.abelbeck.com> > wrote: >> >> sqlite3 /mnt/kd/fossil/astlinux.fossil .dump > >> "$CUSTOM_BACKUP_DIR/astlinux.fossil.dump” > > [snip] > >> This seems to work well with limited testing ... Am I missing anything ? > > That’s more or less what we do here for our off-site backups. The few times > we’ve tried to reconstitute a working .fossil file from one of those backups, > it’s worked. > >> Any issues with the command line sqlite3 being a different version with >> minimal compile time options than the built-in fossil sqlite3 ? > > Probably not, but there’s no reason you have to even bring that worry up: > just use Fossil itself to do the dump: > > $ fossil sqlite3 .dump -R /mnt/kd/fossil/astlinux.fossil ... Thanks Warren, Interesting ... -- # sqlite3 --version 3.20.1 2017-08-24 16:21:36 8d3a7ea6c5690d6b7c3767558f4f01b511c55463e3f9e64506801fe9b74dce34 sqlite3 /mnt/kd/fossil/astlinux.fossil .dump > dump1 -- The dump1 INSERT INTO table names are not quoted. ex: INSERT INTO tag VALUES(1,'bgcolor'); -- # fossil sqlite3 --version -R /mnt/kd/fossil/astlinux.fossil 3.17.0 2017-02-13 16:02:40 ada05cfa86ad7f5645450ac7a2a21c9aa6e57d2c fossil sqlite3 .dump -R /mnt/kd/fossil/astlinux.fossil > dump2 -- The dump2 INSERT INTO table names are "double-quoted". ex: INSERT INTO "tag" VALUES(1,'bgcolor'); I think I will stick to using the native sqlite3 CLI for backups and restores. Of course all the sqlite3 versions will be changing over time anyway. Lonnie _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
