>>>>> "Jason" == Jason Dagit <[EMAIL PROTECTED]> writes:
Jason> So....my proposal is for darcs to be an api which includes
Jason> a way to perform sql queries on the darcs repo database.
Jason> Any takers?
I don't see how you plan to get there from here.
There may be a fundamental problem here. SQL is RDBMS-oriented.
Darcs as currently implemented is an object database with relatively
little interesting table structure. True, each patch has a set of
interesting attributes which could be made into a table, but the
versions are implicit and cannot be accessed by relational operations.
Eg, I don't see how "darcs annotate" could be implemented as an SQL
query. (Don't take that example _too_ seriously, but it does show how
the kind of thing we typically want to do may not really be
well-adapted to SQL.)
I suppose it would not be difficult to implement such a database (eg,
decorate the "weave" archive format that bazaar-ng is developing with
enough information to make it a table usable for that purpose). But
how would you make that compatible with "darcs replace"?
BTW, for the archives of patches and pristines it might be a good idea
to (eventually) go to git as the basic backend. Besides Julius's
interest, Linus is a certified genius, and Tom Lord is basing his v2
Arch architecture (aka revc) on it, so it comes with very good
recommendations.
--
School of Systems and Information Engineering http://turnbull.sk.tsukuba.ac.jp
University of Tsukuba Tennodai 1-1-1 Tsukuba 305-8573 JAPAN
Ask not how you can "do" free software business;
ask what your business can "do for" free software.
_______________________________________________
darcs-users mailing list
[email protected]
http://www.abridgegame.org/mailman/listinfo/darcs-users