Maximilian Roos

Great — it reminded me of parquet, but not in some "don't call it `py`" obvious way — I would go ahead!

> Do you want this to be in a prql-query subdirectory / workspace or should we maybe put this in a separate repo under the prql organisation, e.g. github.com/prql/pq? That's...

Super @snth , very much agree

> @max-sixty Are you happy for me to transfer ownership of the pq repo over to the prql org now and carry on development there? For sure!

> @max-sixty I thought it would send you a request to approve but from my side it appears like it's done nothing. Not sure what the next step is here....

Great!! > Unfortunately now I'm no longer an admin on that repo so can't set up the branch protection and Discord webhook. @max-sixty can you please make me an admin...

Thanks for the issue @sercandogan Generally we'd use an s-string for features that PRQL doesn't yet support, like: ```elm from sometable filter s"json:first_key.second_key" == 1 and s"json:third_key" == 50 ```...

We inherit this from `sqlparser-rs`, this isn't meant as a normative statement! Note that the generic dialect will work for most things; this is only needed for dialect-specific SQL. Please...

`sqlparser-rs` also creates it! We convert into their ast at https://github.com/prql/prql/blob/0.2.6/prql-compiler/src/sql/translator.rs#L52 and then it writes it out. Does that make sense?

I'll close this for the moment, given it relies on a feature upstream. Feel free to reopen if there's something we can do from here. To reiterate, this is not...