On Thu, Oct 6, 2011 at 7:34 PM, Matt Welland <estifo...@gmail.com> wrote:
> Ah, cool!! I assumed the SQLITE error was somehow related to the > non-writablitiy of the file. BTW: the file was not updated because fossil bailed out because of the SQL error. From a user's perspective, the SQL error might not have seemed fatal, and therefore not the source of the problem (i.e. your reaction was perfectly understandable, IMO), but fossil always "fails fast" - if you ever see it emit an error, then it aborted whatever it was trying to do (before it changes anything, more often than not, though a checkout could theoretically fail and still update some of the files). -- ----- stephan beal http://wanderinghorse.net/home/stephan/
_______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
