3 ms·
I usually recommend Q for Mortals. Vhttp://code.kx.com/q4m3/ http://code.kx.com/q4m3/ The thing I love is that the SQL and regular programming syntax can be mi
by is0tope 9y ago
I usually recommend Q for Mortals. Vhttp://code.kx.com/q4m3/ http://code.kx.com/q4m3/
The thing I love is that the SQL and regular programming syntax can be mixed. For instance, if I wish to apply a lambda function for each group I can do, eg:
select result: {lambda code here...} column by category from table
Since a table is implicitly a list of dictionaries under the hood, you can iterate over a table where each column will be a dictionary. Tables and dictionaries are first class objects in q, so it is a lot easier to reason about certain manipulations as they are essentially the same as if you had used regular code. One issue I've always had with SQL itself is that I learned KSQL first, and the way many things are done in regular sql just seem strange.