Hmm, I may not know the internals of how fossil works, but I have these
observations:
* this seems kind of pointless, given I can open the same repo in multiple
locations at the same time. Are you sure you're not referring to the
separate _FOSSIL_ database, instead, or some special operation that changes
that table?
* it doesn't seem to be the actual reason as I ran your query on my various
fossils, and many of them return zero rows or very few rows compared to the
number of opens it went through so far.
* please note that opening the repo using the UI interface, looking around,
and even downloading single files, does not change the database at all. How
can this interface manage to do all this work without a single write to the
database?
-----Original Message-----
From: Andy Bradford
Sent: Saturday, August 09, 2014 8:24 PM
To: Tony Papadimitriou
Cc: Fossil SCM user's discussion
Subject: Re: [fossil-users] How to avoid 'touching' the fossil repo for
read-only operation?
Thus said "Tony Papadimitriou" on Sat, 09 Aug 2014 20:01:30 +0300:
Every time I open a fossil repo, even if I simply open it to just get
a copy of the files in some directory, I end up with a 'touched' repo
file, as if some 'write' operation has occurred in the database.
Every time fossil opens a repository it records the path in the
repository:
$ pwd
/tmp/new
$ echo "SELECT * FROM config WHERE name LIKE 'ckout:%';" | fossil sql
ckout:/tmp/new/|1|1407604257
ckout:/tmp/another/|1|1407604319
Andy
--
TAI64 timestamp: 4000000053e65971
_______________________________________________
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
