Design goal question - is the goal to have a language that blindly compiles to SQL, or will compilation require data schema knowledge?
Suggestion: where possible stick to the well established SQL keywords (prefer "group by" to "aggregate by")
It would really nice to have context when _writing_ the code, so we could do things like autocomplete (IIUC this is what Malloy does already).
Are there features you can think of that would be helpful if we had the schema context during transpiling?
(But otherwise +1 to schema awareness during authoring.)
Indeed — often SQL doesn't know the column _names_, let alone the types. So for cross-column selection (e.g. `across`), this does become necessary.