On Sep 26, 2017, at 9:11 AM, Lonnie Abelbeck <li...@lonnie.abelbeck.com> wrote: > > # fossil sqlite3 --version -R /mnt/kd/fossil/astlinux.fossil > 3.17.0 2017-02-13 16:02:40 ada05cfa86ad7f5645450ac7a2a21c9aa6e57d2c
That would be Fossil 2.0, a transitional release meant to ease the move from Fossil 1.x to 2.x. Why run that version in late 2017? I get staying on 1.37 for legacy support — e.g. because Debian’s still shipping 1.37 in stable, even with the recently-released Squeeze — but 2.0? > 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’); The quotes are both legal SQL and unnecessary, since Fossil doesn’t have spaces or other problematic characters in its table names. But, Fossil 2.3 with a pre-release of SQLite 3.20.0 embedded does not unnecessarily quote identifiers here, for whatever that’s worth. > Of course all the sqlite3 versions will be changing over time anyway. It’s almost certainly fine, particularly in the forward direction. _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
