On Tue, Aug 12, 2014 at 10:29 AM, Baruch Burstein <bmburst...@gmail.com> wrote:
> I am curious how fossil itself manages this. While sqlite DBs (including > the fossil repository) are generally expected to only be read/written with > sqlite software (except for things like Dropbox), and thus only with > "cooperating" programs, how does fossil lock files while it is committing > them? I assume it must somehow keep a file from being changed while it is > in the middle of a commit? > 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). -- ----- stephan beal http://wanderinghorse.net/home/stephan/ http://gplus.to/sgbeal "Freedom is sloppy. But since tyranny's the only guaranteed byproduct of those who insist on a perfect world, freedom will have to do." -- Bigby Wolf
_______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
