Clemens Winter

Thanks for reporting this! Queries like this should work so there's probably some bug that won't be too hard to fix. I'll take a closer look on the weekend.

Actually, the problem looks like it might be caused by `province` being a missing/null column. What do you get when you run the `:memtree` command? What command did you use...

Oh I think I figured out the actual problem, the parser interprets "Ontario" as an identifier for the (non-existent) `Ontario` column. This query should work: `select cumulative_testing from default where...

Correction: single quotes are in fact the correct way to delimit strings in SQL and the only reason it was working for me was because I was testing with an...

> Is it possible to give a better error message in this case? https://github.com/MaterializeInc/materialize gives: `ERROR: column "Ontario" does not exist` in this case. Basically yes, though it's a bit...

There actually used to be support for an OFFSET clause and it looks like the query engine still supports that functionality, it was only unsupported by the new parser but...

Fixed in v0.3.4

I see. Adding just the `row_number()` should be relatively straightforward, but the `OVER (ORDER BY y)` clause is more involved since it requires two separate sort/query passes which the query...

Probably worth giving this a try as well: https://github.com/Amanieu/hashbrown

This query is asking to order by the constant string `'date'`. I'll have to think about what the semantics of that should be, but it's likely not what is intended....