Seems like a lot of people are building databases these days.
I think there is a need for light embedded schemaless databases.
11–20 of 22 posts
Seems like a lot of people are building databases these days.
I think there is a need for light embedded schemaless databases.
How does this compare to SQLite 4's key/value store?
I would say that my objective with ChocoDB is to make it accessible and useful to people who want to manage database structures and queries in a more natural way.
I want the database to help manage different types of relations: inclusion, group, structure, association...
Key/value is simple but it does not help to manage relations. Relational DB don't either help to manage different types of relations.
How does this compare to SQLite 4's key/value store?
I have to look deeper at SQLite4 spec... I would say that my objective with ChocoDB is to make it accessible and useful to people who want to manage database structures and queries in a more natural way. I want the database to help manage different types of relations: inclusion, group, structure, association... Key/value is simple but it does not help to manage relations. Relational DB don't either help to manage dif…
Earlier quoted context omitted.
I have to look deeper at SQLite4 spec... I would say that my objective with ChocoDB is to make it accessible and useful to people who want to manage database structures and queries in a more natural way. I want the database to help manage different types of relations: inclusion, group, structure, association... Key/value is simple but it does not help to manage relations. Relational DB don't either help to manage dif…
Would a graph database be closer to what you are looking to do?
How does this compare to SQLite 4's key/value store?
I have to look deeper at SQLite4 spec... I would say that my objective with ChocoDB is to make it accessible and useful to people who want to manage database structures and queries in a more natural way. I want the database to help manage different types of relations: inclusion, group, structure, association... Key/value is simple but it does not help to manage relations. Relational DB don't either help to manage dif…
they implement couchdb's api and replication, but are implemented in localStorage / sqlite (respectively).
It is not clear to me from the committed CoffeeScript how this will work, but is this going to build on top of ejdb project [0] mentioned here a month or so ago? [0] https://github.com/Softmotions/ejdb
No it's something I've had in mind for many year and that I wanted to build and test before being forced to used MongoDB or EJDB. The source is in /server/reserve.coffee
Why would you do this, instead of just building something on the metal? On a slow platform (ok, an iPhone!) serialization of a 20 field object to a file is approximately 50x faster than running an update statement against SQLite. You are giving up a LOT of performance, even with a platform that's relatively fast, such as SQLite.
Dealing with performance, ChocoDB is currently fast enough for me (2x times slower that classic SQLite ; my first version was 8x slower!)
how does this compare to pouchdb / touchdb? they implement couchdb's api and replication, but are implemented in localStorage / sqlite (respectively).
ChocoDB wants to (re)experiment new ways of dealing with database. It want to keep it simple and accessible.
Earlier quoted context omitted.
I have to look deeper at SQLite4 spec... I would say that my objective with ChocoDB is to make it accessible and useful to people who want to manage database structures and queries in a more natural way. I want the database to help manage different types of relations: inclusion, group, structure, association... Key/value is simple but it does not help to manage relations. Relational DB don't either help to manage dif…
what relations does a relational db not help with? (i thought they were basically an implementation of the relational model).
You can of course manage all those relations in a relational database but the job is done by you, not by the database.