4 ms·
To my way of thinking, "NoSQL" + "local storage" still leaves a lot more in the way of features than just serializing a data structure to disk, or I would be sa
by webmaven 10y ago
To my way of thinking, "NoSQL" + "local storage" still leaves a lot more in the way of features than just serializing a data structure to disk, or I would be satisfied (in Python) with pickle and shelve.
At a minimum I would want:
* Transactions
* Indexing
* A query language
And that is without considering various features that would be specific to particular data store types (or data types).
That said, you could be right that it isn't a problem most developers have, and for those that do, existing solutions fill the niche adequately.
- jerf 10y ago"That said, you could be right that it isn't a problem most developers have," What I mean isn't that it isn't a problem, but more that it isn't a problem acute enough to make people go looking for solutions. By sheer coincidence, I was actually writing some code today that implements an API that backs to many DBs, sorta a crappy NoSQL layer, backing to Postgres. And I had to write the test suite to work against Postgres. I already have the test suite running against SQLite, but there's enough differences that it's not a relevant test. I have to bring up the "real thing". I suspect that's just what most people do.