5 ms·
Pretty telling for the “look SQL is so easy!” example to have a bug.. :) As mentioned in a sibling comment, Kusto Query Language^1 is potentially more readable
by jakear 6y ago
Pretty telling for the “look SQL is so easy!” example to have a bug.. :)
As mentioned in a sibling comment, Kusto Query Language^1 is potentially more readable here:
> SELECT player_name, COUNT(*) as num_hits FROM baseball_players WHERE result='base_hit' GROUP BY 1;
baseball_players
| where result=‘base_hit’
| summarize num_hits = count() by player_name
| project player_name, num_hits
1: yes this is msft specific, yes I work at msft, no not on that team. Just a happy user. The point is the overall pipeline concept more than msft’s specific implementation. 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...
- deleted 6y ago[deleted]
- ethbr0 6y agoThe biggest benefit to anything approaching pipelining is making data-interactive developers think about intermediate and transient state. In my enterprise coding experience, most app developers don't thing of db's as anything other than "one, current state." Which makes debugging a nightmare.
- edmundsauto 6y agoI’d love to hear more of your thoughts on this - I hadn’t considered DBs as a form of state. Obviously they are, it just hasn’t occurred to me. If I may borrow a related concept - what other mental models should I CASCADE the implications of this new perspective to? Ie, how does this change how you approach problems? Are there limits where you would call out?
- edmundsauto 6y agoHow dare you underestimate me! I would have screwed up the query in any language ;) This is also quite readable, no arguments there! I personally think SQL is a great language for broad appeal. I understand why people don't like it - there are many funky aspects - but I also understand why it's become dominant. Because it's just so damn useful. WRT the MS specific language, my issue there is portability of knowledge. Someone with experience in say Oracle, 20 years ago, can reuse those skills with SQL. IMO, we need more common-language, independent-implementation tools like SQL in order to enable more people to code.