One of the nicest things you can do with this is get hierarchical results.
JSON with Sqlite
71–74 of 74 posts
Re: JSON with Sqlite
#72This should be build in standard SQLite.
The documentation specifies that that is a possible end state:
> The "1" at the end of the name for the json1 extension is deliberate. The designers anticipate that there will be future incompatible JSON extensions building upon the lessons learned from json1. Once sufficient experience is gained, some kind of JSON extension might be folded into the SQLite core. For now, JSON support remains an extension.
Re: JSON with Sqlite
#73Earlier quoted context omitted.
I work quite a lot with SQLite since is the foundation of https://redisql.com/ The JSON module is really a god send! It allows to do things that otherwise would be extremely painful, difficult or not ergonomic. Just to take few examples, here ( http://redbeardlab.tech/rediSQL/blog/JaaS/ ) is a simple way to store JSON and doing manipulation on it, it would have been impossible without the JSON module. In this other e…
RediSQL looks interesting and I like the pricing structure. I'm working on marketing my own set of products so I know it's difficult to keep it up. Good luck with this venture and I hope it works out for you and your team.
Great!
Please get in touch, there is my email in the profile! There is a small community of people that try to live with open source software.
If your product is somehow usable with RediSQL we could do marketing together or bundle our products, there are a lot of synergy in software that can be enhanced.
Re: JSON with Sqlite
#74Earlier quoted context omitted.
Often people use SQLite for sheer convenience instead of perceived performance or resource efficiency i.e. because SQLite is zero config, works out of the box. Sure spinning up a docker container with PostgreSQL is easy enough but why do that when you can use the default standard library with SQLite already embedded and linker configed?
SQLite is an alternative to fopen not a full blown DB... And it’s performance and reliability are a huge part of why it runs on millions of devices everywhere. Your browser was never going to embed a build of PostgreSQL and Docker. Enabling WAL can hardly be called config, it’s a one liner in every driver I’ve ever seen. It’s like saying specifying the file directory SQLite uses is config.
> It’s like saying specifying the file directory SQLite uses is config.
Or, to continue the fopen analogy, like saying that the file you've given fopen is to be opened with mode "a+". The only real difference is that fopen's mode argument is required whereas SQLite's mode has a useful default.
> Enabling WAL can hardly be called config, it’s a one liner in every driver I’ve ever seen.
Even in the raw libsqlite3 C API (as long as you don't need any error checking ;) ):
sqlite3_exec(db, "PRAGMA journal_mode=WAL", NULL, NULL, NULL);