5 ms·

Show HN: LanderDB – A Mini Flat File Database Engine for Python

27 points by max0563 11y ago

smt88 11y ago
What's the use-case for this over, say, SQLite?
- max0563 11y ago
  It was mainly created for P2P systems that need to sync databases across clients. Being that data is stored in JSON it can be sent and received with relative ease.
  - _ZeD_ 11y ago
    ...duh... instead a sqlite file is so difficult to share?
    - togusa 11y ago
      Why use sqlite when you can invent something new which has no concurrency semantics and eats up inodes?
      - amirouche 11y ago
        sqlite is thread safe?
        klibertp 11y ago
        Yeah, I remember reading about it a couple of months (years?) ago and being very surprised and impressed. The details: https://sqlite.org/threadsafe.html https://sqlite.org/threadsafe.html
  - smt88 11y ago
    SQLite databases are just as "easy" to send and receive. In fact, they can be compressed, which means they're even easier.
- klibertp 11y ago
  I think it's use-case is when your data is more structured than what Berkeley DB can handle but doesn't really fit neatly into tables. Not using SQL as a query language is a plus in some scenarios too, particularly if your data manipulation needs are a bit more complex and you don't have the room for importing and using a full ORM (which is a "Vietnam of Computer Science"[1] anyway). [1] http://blogs.tedneward.com/2006/06/26/The+Vietnam+Of+Computer+Science.aspx http://blogs.tedneward.com/2006/06/26/The+Vietnam+Of+Compute...
  - biokoda 11y ago
    Sqlite now supports JSON.
    - smt88 11y ago
      You still have to use SQL to query it though, right? JSON is just a data type option, to my knowledge.
      - biokoda 11y ago
        When is it better to use something else?
        smt88 11y ago
        Oh I personally have no problem with SQL. Another commenter was just saying you might want to use LanderDB when you don't want to use SQL.
  - deleted 11y ago
    [deleted]
  - smt88 11y ago
    It sounds like you're describing an embeddable document store. There are options for that as well: - UnQLite: http://charlesleifer.com/blog/python-bindings-for-unqlite-an-embedded-nosql-database-json-document-store/ http://charlesleifer.com/blog/python-bindings-for-unqlite-an... - tinydb: https://pypi.python.org/pypi/tinydb/ https://pypi.python.org/pypi/tinydb/ - Blitz: https://github.com/adewes/blitzdb https://github.com/adewes/blitzdb
kabdib 11y ago
Hmmm. Not really a database; not much different than a "config file" container. No ACID, doesn't even attempt a filename flip (that would be an easy addition). As it stands, get interrupted during an update and your data's gone.

27 points by max0563 11y ago

smt88 11y ago

What's the use-case for this over, say, SQLite?

max0563 11y ago
It was mainly created for P2P systems that need to sync databases across clients. Being that data is stored in JSON it can be sent and received with relative ease.
- _ZeD_ 11y ago
  ...duh... instead a sqlite file is so difficult to share?
  - togusa 11y ago
    Why use sqlite when you can invent something new which has no concurrency semantics and eats up inodes?
    - amirouche 11y ago
      sqlite is thread safe?
      - klibertp 11y ago
        Yeah, I remember reading about it a couple of months (years?) ago and being very surprised and impressed. The details: https://sqlite.org/threadsafe.html https://sqlite.org/threadsafe.html
- smt88 11y ago
  SQLite databases are just as "easy" to send and receive. In fact, they can be compressed, which means they're even easier.
klibertp 11y ago
I think it's use-case is when your data is more structured than what Berkeley DB can handle but doesn't really fit neatly into tables. Not using SQL as a query language is a plus in some scenarios too, particularly if your data manipulation needs are a bit more complex and you don't have the room for importing and using a full ORM (which is a "Vietnam of Computer Science"[1] anyway). [1] http://blogs.tedneward.com/2006/06/26/The+Vietnam+Of+Computer+Science.aspx http://blogs.tedneward.com/2006/06/26/The+Vietnam+Of+Compute...
- biokoda 11y ago
  Sqlite now supports JSON.
  - smt88 11y ago
    You still have to use SQL to query it though, right? JSON is just a data type option, to my knowledge.
    - biokoda 11y ago
      When is it better to use something else?
      - smt88 11y ago
        Oh I personally have no problem with SQL. Another commenter was just saying you might want to use LanderDB when you don't want to use SQL.
- deleted 11y ago
  [deleted]
- smt88 11y ago
  It sounds like you're describing an embeddable document store. There are options for that as well: - UnQLite: http://charlesleifer.com/blog/python-bindings-for-unqlite-an-embedded-nosql-database-json-document-store/ http://charlesleifer.com/blog/python-bindings-for-unqlite-an... - tinydb: https://pypi.python.org/pypi/tinydb/ https://pypi.python.org/pypi/tinydb/ - Blitz: https://github.com/adewes/blitzdb https://github.com/adewes/blitzdb

kabdib 11y ago

Hmmm. Not really a database; not much different than a "config file" container. No ACID, doesn't even attempt a filename flip (that would be an easy addition). As it stands, get interrupted during an update and your data's gone.