Tobias Brandt

Very much agree with your comments regarding sticking to linear recursion for now and our proposed syntax would also show that this is iteration and might demystify "Recursive" CTEs for...

A potentially rich source of Recursive CTEs: https://hub.getdbt.com/jpmmcneill/dbt_graph_theory/latest/

Example from: https://twitter.com/matsonj/status/1621031377616646144 (in turn from https://youtu.be/pVklntbGiNo?t=220).  First attempt at rewriting this in the proposed PRQL syntax. I think we don't have two of the constructs yet (ARRAY and...

A problem with the query above is that `paths` shouldn't actually be exposed in the scope of the main pipeline because it's only defined in the lambda argument of `loop`....

The [`loop` example from the book](https://prql-lang.org/book/language-features/standard-library/loop.html) ```elm from_text format:json '[{"n": 1 }]' loop ( filter n

> In SQL, RECURSIVE be used only directly after WITH keyword. ... So I constructed a CTE that contains a nested WITH clause, which can be recursive, since it is...

> I still don't quite understand what loop_name= would mean here. > > Which one of these two would it allow? Both! If you look at the example SQL for...

I like you approach @aljazerzen . It's very cool that you can detect the patterns in the RQ, regardless of how they were generated, and then produce the SQL from...

I was going to raise a question about the names as well. I think at least for `intersection` we could go with the shorter `intersect` which is still valid English...

Looks like [DuckDB](https://duckdb.org/docs/sql/query_syntax/setops.html) follows SQLite here. If I understand the Postgres docs correctly, then `EXCEPT ALL` does actually the opposite of what I would expect (just from the English), i.e....