41–50 of 88 posts
https://github.com/stochastic-technologies/goatfish
It also supports indexing on arbitrary fields and is only a few lines of code. It did come in very handy.
I would love an embeddable nosql database engine but this isn't it. I'm looking for something like MongoDB but embeddable. RaptorDB comes close but it doesn't have full support for Mono yet. https://raptordb.codeplex.com/ Can anyone recommend one?
Honestly, you could build a decent embedded document store on top of SQLite pretty easily. It's hard to beat SQLite's long and solid track record for embedded data persistence. The default BLOB limit is around 1GB. http://www.sqlite.org/limits.html
Nice, I'm currently using SQLite for key value storage, because there aren't better light options afaik. Python shelve module is totally useless with multi gigabyte tables and millions of keys.
I would love an embeddable nosql database engine but this isn't it. I'm looking for something like MongoDB but embeddable. RaptorDB comes close but it doesn't have full support for Mono yet. https://raptordb.codeplex.com/ Can anyone recommend one?
Can I ask why? From my other comment on this article I don't see the use case for an embedded NoSQL, but I'd like to. Where and how would you use it? What, if anything, do you currently use in its place? If nothing, is there something you could use instead? Why is it better than a serializing your own domain model (assuming you have a domain model), or other alternatives?
These are all the things I'm used too using in MongoDB, I don't want to go back to SQL type databases. I thought I saw a SQLite driver that mimicked a MongoDB like system but I can't seem to find it.
I would love an embeddable nosql database engine but this isn't it. I'm looking for something like MongoDB but embeddable. RaptorDB comes close but it doesn't have full support for Mono yet. https://raptordb.codeplex.com/ Can anyone recommend one?
Honestly, you could build a decent embedded document store on top of SQLite pretty easily. It's hard to beat SQLite's long and solid track record for embedded data persistence. The default BLOB limit is around 1GB. http://www.sqlite.org/limits.html
It doesn't explain the advantages over all the other dbm alternatives: http://en.wikipedia.org/wiki/Dbm#Successors I'm yet to see a good replacement to Kyoto cabinet both in terms of ease of use and performance. I feel it'd be better energy to pick up kyoto cabinet and maintain it than re-write something from scratch.
Nice, I'm currently using SQLite for key value storage, because there aren't better light options afaik. Python shelve module is totally useless with multi gigabyte tables and millions of keys.
What's wrong with BerkleyDB, Tokyo Kabinet, Kyoto Kabinet, LevelDB .. ? It's a real question because I haven't actually used them. SQLite is fine, but if you don't need sql they probably fare better.
Earlier quoted context omitted.
Can I ask why? From my other comment on this article I don't see the use case for an embedded NoSQL, but I'd like to. Where and how would you use it? What, if anything, do you currently use in its place? If nothing, is there something you could use instead? Why is it better than a serializing your own domain model (assuming you have a domain model), or other alternatives?
Probably a better description would be an embeddable document store is what I'm looking for. I want to store my objects in the database without having to flatten out its nested structure. I also want to be able to search those nested structures. I want the database engine to handle creating the fields if they don't exist. I don't want to deal with schemas. Each document in a collection should not care if the fields a…
Would something like this fit the bill? http://www.db4o.com/s/monodb.aspx