4 ms·
Interesting. I've never seen SQL as a limiting factor, since 99% of the cases I use I just need to get something by it's id or a simple query (select, join, whe
by not_knuth 6y ago
Interesting. I've never seen SQL as a limiting factor, since 99% of the cases I use I just need to get something by it's id or a simple query (select, join, where, order).
And it's really easy to learn too. I've seen many people without coding background pick it up and this is definitely a bonus where I work. Otherwise that 1 CS/Data Science guy is pre-occupied with hammering out queries for everyone.
What kind of limitations do you run into? And what alternative do you propose (besides GraphQL)?
- jakear 6y agoNot the parent, but I quite like the Kusto query language. It’s Microsoft specific, but the overall concept is nice and could be implemented more broadly. The operations are described as a pipeline, which to me is much more readable (and writable!) than SQL, where it feels like I’m always bouncing my mental cursor around to figure out what a query is doing. I’m sure that’d reduce with more SQL exposure, but understanding Kusto came pretty much instantly for me. Also, each operation being its own line in the pipeline makes modification an absolute breeze, simply comment out, reorder, etc lines and the result will usually also be a valid query. https://docs.microsoft.com/en-us/azure/data-explorer/kusto/query/tutorial?pivots=azuredataexplorer https://docs.microsoft.com/en-us/azure/data-explorer/kusto/q...
- iudqnolq 6y agoKusto looks very similar to the Ecto DSL for SQL queries (elixir library). I really like the pipeline operation, I wish more languages added it. https://hexdocs.pm/ecto/Ecto.Query.html#module-macro-api https://hexdocs.pm/ecto/Ecto.Query.html#module-macro-api
- elygre 6y agoI was reading the same parent post, also thinking about kusto! It really is very nice. It would be super interesting to see how it would fit on top of Postgres or Oracle.