3 ms·

Maybe you should just think of it as the NoSQL version of sqlite3 but with added version control.

• jemfinch 16y ago
  What does that even mean?
  • deleted 16y ago
    [deleted]
  • JoachimSchipper 16y ago
    I think "easy to set up" combined with "less crappy than expected". Although SQLite isn't very crappy at all...
  • chopsueyar 16y ago
    Because sqlite stores everything in a flatfile, so your are just doing version control on flatfile changes.
  • po 16y ago
    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.
• deleted 16y ago
  [deleted]