News for hackers. Stuff that matters.
Re:Git as a NoSQL datastore by technoweenie on Monday November 22, 2010 @01:58AM (#1928970)
What global lock? Are you talking about the index? There are options for writing the index to separate directories. You can write each blob/tree separately, build an index in a unique temporary directory, and then the commit.

Is there something else I'm missing?

Re:Git as a NoSQL datastore by pauldowman on Monday November 22, 2010 @08:34AM (#1929706)
GitModel itself has a global lock (for now), here: https://github.com/pauldowman/gitmodel/blob/master/lib/gitmo...

I think it's easily fixed with a merge, as I described here: http://news.ycombinator.com/item?id=1929691

Re:Git as a NoSQL datastore by fhars on Monday November 22, 2010 @02:12AM (#1928999)
Concurrent updates to the same object.

You could get around some of the limitations by creating a branch for every session (though probably not on a high volume site), but then you will have lots of interesting problems once a session ends and you have to merge all changes back into master.

Re:Git as a NoSQL datastore by technoweenie on Monday November 22, 2010 @02:14AM (#1929003)
Ahh, yes this would be a problem on GitModel. I was thinking of Git at a lower level, since you can't update objects without also changing the SHA.