that replaces tables/joins with a lightweight semantic binding layer
But then the included example doesn't do any joins. :(
Similarly, the "Concepts" section of the documentation has a diagram about joins, but no code examples.
On a more-technical note, the generated queries seem to use a LOT of CTEs. While they aren't a strict optimization barrier in PG anymore, there are definitely situations where they'll fall back to materialization - and the generated SQL seems to commonly build a "all of the rows" CTE and then apply conditions in a subsequent one.
General comment: the README opens with
But then the included example doesn't do any joins. :(Similarly, the "Concepts" section of the documentation has a diagram about joins, but no code examples.
On a more-technical note, the generated queries seem to use a LOT of CTEs. While they aren't a strict optimization barrier in PG anymore, there are definitely situations where they'll fall back to materialization - and the generated SQL seems to commonly build a "all of the rows" CTE and then apply conditions in a subsequent one.