Maximilian Roos
Maximilian Roos
```elm func sum method -> s"sum(method)" from x aggregate [ sum credit_card, ] select credit_card ``` compiles to ```sql SELECT credit_card FROM x ``` ...which doesn't look correct :)
An infix operator is probably worthwhile given how often regex matching is used. Most implementations use a normal function like `REGEXP` or `REGEXP_CONTAINS`. Postgres uses `~=`, and `!~` for negation....
To confirm whether there's an error on https://github.com/mitsuhiko/insta/issues/227 (though given build issues we may not be able to resolve this)
Following on from https://github.com/prql/prql/issues/430 Check out how mypy playground does this — it uses GitHub to provide a backend for saved queries, so no state is required: https://mypy-play.net/?mypy=latest&python=3.10&gist=b2c27a5ca4aad9e8ce63cd74dc4032b0 > Gist...
We have a [stdlib](https://github.com/max-sixty/prql/blob/main/src/stdlib.prql), written by @qorrect , which provides some standard functions by using s-strings. We could fill this out with some more standard functions — e.g. `EXP`, `MOD`,...
@qorrect raises an interesting point on a [Discord thread](https://discord.com/channels/936728116712316989/939181039924944947). Something I find frustrating about SQL is that a query result can have three types: - a table - a column...
I've been spending some time looking at [Malloy](https://github.com/looker-open-source/malloy), a language from Looker that looks promising. I've been a fan of @lloydtabb's for a while, and briefly chatted to him about...
For creating "structs" / "objects" / "composite types" — e.g. [snowflake objects](https://docs.snowflake.com/en/sql-reference/data-types-semistructured.html#characteristics-of-an-object), [postgres composite types](https://www.postgresql.org/docs/current/rowtypes.html), [bigquery structs](https://cloud.google.com/bigquery/docs/reference/standard-sql/data-types#struct_type), what do people think of syntax? We could use brackets for this: ```elm...
Following on from https://github.com/prql/prql/issues/367, we'd like to add versioning to PRQL, so that we can make changes to the PRQL language without breaking lots of existing code. I'm not sure...