@ngn should i have expected this to be rectangular, or is the ragged output the way it should be? ngn.bitbucket.io/k/…

@chrispsn this is a side effect. i hadn't even thought about it

there is something not quite right there - it shouldn't mention e or f at all

@chrispsn the current impl is the k string on this line

@ngn oh nice, didn't realise it was a k string

was thinking 'deep where' could also be useful for processing the result of a scan

i'm so used to the primitives as is, that it's nice to go back to old problems and see if it suggests a new approach

is the by clause in k9/ksql nyi, or replaced with: g group select a from t ?

@ktye is the "select[G]" part here new?

@coltim idn. can you get it to work?

@ktye nope! although I'm not super familiar with k9

not sure what t:[[]a:1 1 1 2 2 3;b:"abcdef"];select[t:a] from t where a=1 is doing. weirdly select[t:a] by from t where a=1 returns the same

not sure about the by part but yeh that's just parsed as select [t:a] from t

what is parse? used to be `p@

dyadic $ is listed as parse, although it's still pad too

@coltim that's type from string, e.g "f"$"2.34"