On Thu, Dec 17, 2009 at 8:32 AM, Petr Baudis <[email protected]> wrote: > On Thu, Dec 17, 2009 at 05:27:20AM -0800, Ido Ran wrote: >> So my question is how can git still be used as database backend. >> I'm open for ideas, I just don't see it yet. > > Then why do you actually want to do it? :-) It's not clear what your > goals are, you should specify them first, then check how can (or can't) > git fit the goals. >
I'm not sure that git is a good candidate for a direct replacement for a database per se. However I can think of applications which currently use, say relational databases, which might be better served by a 'versioned file system' like git. One example is a wiki. Ward Cunningham's original wiki used (probably still uses) the file system to save the wiki pages, and relied on users to manually weed out unwanted changes. Wikipedia uses a complex relational database to save wiki pages and provide version control. Building a wiki on git would seem to be a fairly natural idea, but I don't think that the interface between the app and git would look like a relational db api. -- Rick DeNatale Blog: http://talklikeaduck.denhaven2.com/ Twitter: http://twitter.com/RickDeNatale WWR: http://www.workingwithrails.com/person/9021-rick-denatale LinkedIn: http://www.linkedin.com/in/rickdenatale -- You received this message because you are subscribed to the Google Groups "Git for human beings" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/git-users?hl=en.
