On 3/13/2017 1:45 PM, Richard Hipp wrote:
On 3/13/17, Ross Berteig <r...@cheshireeng.com> wrote:
So to move an existing project to the latest fossil after an SHA3-named
artifact exists, it appears to be necessary to rebuild existing repos
with version 2.0 or later so the database schema don't include a
constraint that forbids SHA3 names.
Not, not exactly.
A rebuild is not necessary. But you do need to access the repo once
(perhaps by running "fossil dbstat") in order to cause the minor CHECK
constraint update to occur. Rebuild will do that, but it is more work
than is actually needed. So, there is no harm in doing a rebuild, but
it is not strictly necessary.
And dbstat has the advantage of being both fast and available as "fossil
all dbstat" allowing most of my clones to be touched.Good to know.
--
Ross Berteig r...@cheshireeng.com
Cheshire Engineering Corp. http://www.CheshireEng.com/
+1 626 303 1602
_______________________________________________
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
