On Tue, Aug 12, 2014 at 7:18 AM, Baruch Burstein <[email protected]> wrote:
> On Tue, Aug 12, 2014 at 1:35 PM, Stephan Beal <[email protected]> > wrote: > >> >> For the most part, fossil only works with sqlite dbs, so it leaves the >> locking/transactions to sqlite. It does not do any handling of locking of >> non-db files (e.g. source files). >> > > I was referring to the source files. Fossil doesn't lock them? Can't that > cause problems with them getting changed in the middle of committing them? > > After loading all content in the repo, but before committing the transaction, SQLite goes back and double-checks that the content on disk exactly matches the content in the repo. The transaction rolls back if not. -- D. Richard Hipp [email protected]
_______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
