Phil Rzewski

@SoftTools59654: I've moved your issue to the Zed repository and re-framed it in what I think is a more accurate way. Right now the Zed language keywords like `count` are...

Verified in super commit 2965a1d. Per linked PR #5404, as part of the work on evolving the language into SuperSQL, function names are now case insensitive in the parser. For...

@SoftTools59654: Thanks for the suggestion. I've moved this issue to the Zed repo since it's something that would have to be addressed at that layer before we could support it...

This has been addressed at the Zed (now SuperDB) layer via PR https://github.com/brimdata/super/pull/5570 with related docs changes in https://github.com/brimdata/super/pull/5571 and https://github.com/brimdata/super/pull/5572. Development in Zui (soon to be renamed to SuperDB...

I recently bumped into another variation of this while helping a user in a [community Slack thread](https://brimdata.slack.com/archives/CTSMAK6G7/p1733955630291719). Their specific example: > optimization question - every step here makes sense to...

Another related example from a recent [community Slack thread](https://brimdata.slack.com/archives/CTSMAK6G7/p1736636477332389). In the user's own words: > can I "flatten" or "merge" records together? (not zq's use of flatten). These examples work...

I think I see a use case for this in the super era. Some SQL tutorials show examples involving zip codes, which might have leading zeroes. Consider test data `zipcodes.csv`:...

Hi @chrismo! It's true that not 100% of what's in "specs" docs (such as within the [Formats](https://superdb.org/docs/formats/) section) are yet fully implemented in the SuperDB tools. I can see how...

@cho-m: Thanks for giving it a look! Your comment made it sound like it was worth a test, so I just ran through the same repro steps in with my...

Thanks for the update @cho-m! That all sounds encouraging. Regarding your second bullet, since you said the Cask would get installed and take precedence it seems that'll get to the...