Re:Git as a NoSQL datastore
by jemfinch on Monday November 22, 2010 @05:19AM
(#1929322)
What does that even mean?
[ Parent
| on HN ]
Re:Git as a NoSQL datastore
by JoachimSchipper on Monday November 22, 2010 @06:23AM
(#1929427)
I think "easy to set up" combined with "less crappy than expected". Although SQLite isn't very crappy at all...
Sqlite is often used as a quick and dirty database by projects that don't want to burden their developers with the setup overhead of mysql or postgres.
It's a tiny, rock-solid executable that stores data in a single binary file and supports sql access. Access to the file is globally locked. It's good enough for testing out a project on a single developer's machine but the global lock makes it hard to use in a multi-user production scenario.
In a similar vein I could see git as a widely available, rock-solid, "quick and dirty" way for a project to store and retrieve documents.
Re:Git as a NoSQL datastore
by chopsueyar on Monday November 22, 2010 @08:43AM
(#1929729)
Because sqlite stores everything in a flatfile, so your are just doing version control on flatfile changes.