On Wed, Aug 6, 2014 at 3:14 PM, Richard Hipp <d...@sqlite.org> wrote:
> > Advisory locks are used. So cooperating programs know to not have two > programs writing at once. But Dropbox is not a cooperating program in this > context. Dropbox just opens the file and writes, without paying any > attention to the advisory locks. > 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? -- ˙uʍop-ǝpısdn sı ɹoʇıuoɯ ɹnoʎ 'sıɥʇ pɐǝɹ uɐɔ noʎ ɟı
_______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
