will try that. thanks. about the other suggestion to WAL mode, do you generally think that is a better way to run sqlite whenever there is any chance of concurrency? I was under the impression that it should work fine either way, but WAL just might provide some quicker response without having to wait on a locked DB file, but with other potential disadvantages which I can’t remember what they are right now..
On May 3, 2016, at 11:58 AM, Richard Hipp <d...@sqlite.org> wrote: > On 5/3/16, Steve Schow <st...@bstage.com> wrote: >> This particular repo is not a clone of another repo. >> And it appears to be trying to sync with itself. > > Huh. I don't know how you got it into that state. > > The solution is probably "fossil remote off". > > > -- > D. Richard Hipp > d...@sqlite.org > _______________________________________________ > fossil-users mailing list > fossil-users@lists.fossil-scm.org > http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
