On Sat, Mar 31, 2012 at 01:31:15AM -0700, Ashod Nakashian wrote:
> ::Summary::
Thanks for summarizing the discussion.
This summary was very useful to me.
> 3) Sqlite has a very reputable code-base and performance, in addition
> to already being utilized by SVN. A proposal to use it for small
> pristine file storage has been proposed. The major advantage is the
> possibility of abusing and/or overloading Sqlite with this kind of
> usage that it probably isn't optimized to handle.
Sqlite should be capable of handling this well.
Are you aware of fossil (http://fossil-scm.org)?
This is the version control system used to manage sqlite, and not
surprisingly it stores all of its revision and working copy meta
data in sqlite. Fossil is kept very simple at its core and might
have scalability issues with very large projects (such as webkit)
but nevertheless it is very inspiring. It might be worthwhile to
take a look at the details of how fossil stores revision file data
(because fossil is a distributed version control system the pristine
files are simply stored in the last committed revision).
I haven't yet spent enough time thinking about compressed pristines
to have an opinion about which approach we should take. But I'm very
much looking forward to seeing a patch that implements a first step
or first milestone of whichever approach we're going to settle on.
I'm glad to see somebody driving this feature forward. Thanks!
Received on 2012-04-01 01:47:48 CEST