On Dec 28, 2005, at 9:04 AM, Richard A. Smith wrote:
Jason Dagit wrote:
and so on can be whatever. My goal in this direction is to
experiment with using a database (sqlite in particular) as the
datastore for many of these things. I know that changing the
patch format could fix
I think using sqlite for stuff is a excellent idea. I've used
sqlite and its _really_ nice. The manifest typing and automatic
sizing of v3 is awesome. It would also mean that the data would be
accessible from a number of alternate methods.
I haven't started factoring the code yet, I'll probably wait till the
new year to start that. I'm fixing bugs and looking/thinking about
what I want the end result to be like first. Since I'm not expert at
relational databases I'm sure I'll have lots of questions on this
list asking for advice about storing the data in tables. And yes,
having the data accessible to alternative methods is a goal. I'd
like to increase the ability to "inspect" darcs repos. It could lead
to better tool support (visualizations and history browsers).
Do you think it would be possible to convert the entire repo over
to sqlite or just a lot of additional meta-data?
I had envisioned storing everything in _darcs in a database (and
possibly doing away with pristine) so that you could just move the db
and you would have moved the repo. But maybe pristine should stick
around in addition to the db.
I would also welcome the C API. Its on my list to start trying to
grok haskell but I've a long way to go.
You're not alone. And I think that it's great to have a version
written completely in haskell to help showcase how wonderful haskell
can be. On the other hand, I think darcs would see more and faster
front end development if other languages were an option.
Thanks,
Jason
_______________________________________________
darcs-users mailing list
[email protected]
http://www.abridgegame.org/mailman/listinfo/darcs-users
