20 ms·

PRQL fixes this. (Disclaimer: I'm a PRQL contributor.)

• zX41ZdbW 3y ago
  Not only PQRL fixes this. It has been allowed in ClickHouse's SQL since its inception.
  • snthpy 3y ago
    That's awesome! ClickHouse is a great system by all accounts and I've been meaning to try out ClickHouse Local. I'm more familiar with DuckDB and they've also been doing some great innovation on the SQL front. I don't know offhand if they can also do the forward referencing thing but they allow putting the FROM first and having GROUP BY ALL etc.. It's great to see all this innovation happening in the SQL and Query Language space more generally at the moment.
    • zX41ZdbW 3y ago
      It is strange to hear about innovation in DuckDB - I see that they are gradually re-implementing the stuff already existing in ClickHouse. Sometimes they do a better job at promoting it.
      • snthpy 3y ago
        That's probably true but the big differentiator was that DuckDB can run in your python process so there's very low fiction to adopt it. My impression of ClickHouse was that it was more like postgresql in that regard, i.e. OLAP : OLTP as ClickHouse : Postgres as DuckDB : SQLite. clickhouse-local may have closed the gap on that though. Can you embed it in Python as a library?
        • zX41ZdbW 3y ago
          > Can you embed it in Python as a library? https://github.com/chdb-io/chdb https://github.com/chdb-io/chdb pip install chdb
      • glogla 3y ago
        They also do bunch of stuff that ClickHouse can't do, like correlated subqueries [1] or recursive CTEs. I kinda wish for a database with ClickHouse storage and DuckDB optimizer. At least my experience with ClickHouse is that MergeTree is incredibly good at what it does, but the optimizer hurts. [1]: https://duckdb.org/2023/05/26/correlated-subqueries-in-sql.html https://duckdb.org/2023/05/26/correlated-subqueries-in-sql.h...