Re:Git as a NoSQL datastore
by technoweenie on Monday November 22, 2010 @02:00AM
(#1928972)
Git doesn't give you merges, it gives you merge conflicts. I find it similar to how Riak uses vector clocks (http://blog.basho.com/2010/01/29/why-vector-clocks-are-easy/). It knows enough to tell you there's a conflict, but requires you (or the app) to tell it which version is the right one.
Re:Git as a NoSQL datastore
by pauldowman on Monday November 22, 2010 @08:40AM
(#1929722)
Right, it's either a trivial merge when you commit the transaction, or it's a conflict (i.e. two transactions updated the same attribute of the same entity).
There's no automatically fixing a conflict so the second transaction fails. Since there's full isolation that's pretty standard optimistic locking: http://en.wikipedia.org/wiki/Optimistic_locking
In most cases the transaction would succeed if it was automatically retried.
Also, you're not taking into account the things that Git does give you that typical databases don't, like branching and merges