A project I'm using, which I'm also one of the authors of, is OctoSQL[1].
It allows you to transform and join data from different data sources (including databases like mysql, postgres, redis, and CSV or JSON files, more to come) using a familiar interface - plain SQL.
Other than that, I like Exploratory[2].
And for nested JSON data I use another project of mine, jql[3] - an easier to use (in my opinion) lispy alternative to jq. (originally inspired by a hackernews comment actually)
Interesting project and I like the name. It seems that the underlying relationship in each data source has to be relational though (even for JSON files) - is that a fundamental limitation of using SQL as the glue language, or are there plans to integrate hierarchical models of data in some form as well?
Comments
A project I'm using, which I'm also one of the authors of, is OctoSQL[1].
It allows you to transform and join data from different data sources (including databases like mysql, postgres, redis, and CSV or JSON files, more to come) using a familiar interface - plain SQL.
Other than that, I like Exploratory[2].
And for nested JSON data I use another project of mine, jql[3] - an easier to use (in my opinion) lispy alternative to jq. (originally inspired by a hackernews comment actually)
[1]:https://github.com/cube2222/octosql
[2]:https://exploratory.io
[3]:https://github.com/cube2222/jql
Interesting project and I like the name. It seems that the underlying relationship in each data source has to be relational though (even for JSON files) - is that a fundamental limitation of using SQL as the glue language, or are there plans to integrate hierarchical models of data in some form as well?
If you mean hierarchical data querying (like nested json, or json in sql rows), then that's very high on our radar.
OctoSQL sounds interesting thanks.