I use duckdb and looked into clickhouse-local. The dealbreaker for me was that clickhouse-local supported only a subset of SQL (that most people would probably be ok with, but not sufficient for a lot of complex analytics work). For instance, clickhouse doesn't support lead/lag functions natively (though it does propose workarounds).
DuckDB's SQL coverage is much more complete and matches my experience with full blown databases like Postgres and Redshift.
As well, performance-wise DuckDB is currently still somewhat faster than clickhouse-local [1] but I would say this is a secondary consideration -- as long as either is "fast enough for your purposes" this shouldn't be an issue -- and clickhouse is plenty fast.
The primary consideration for me would be the SQL support. That said, if you don't use any complex SQL, clickhouse-local seems like it would be a worthy contender.
> The dealbreaker for me was that clickhouse-local supported only a subset of SQL
Yeah, I think there was some advanced psql stuff that I wanted to do with duckdb but wasn't able, so I can imagine that with clickhouse-local it would be even worse. Not that duckdb isn't enough for me.
Now I need to make my mind about duckdb vs nushell. Both are greats. Well I can use both, maybe.
Here's clickhouse's SQL support: https://clickhouse.com/docs/en/sql-reference/
Compare this to DuckDB's (on the sidebar): https://duckdb.org/docs/sql/introduction
DuckDB's SQL coverage is much more complete and matches my experience with full blown databases like Postgres and Redshift.
As well, performance-wise DuckDB is currently still somewhat faster than clickhouse-local [1] but I would say this is a secondary consideration -- as long as either is "fast enough for your purposes" this shouldn't be an issue -- and clickhouse is plenty fast.
The primary consideration for me would be the SQL support. That said, if you don't use any complex SQL, clickhouse-local seems like it would be a worthy contender.
[1] https://benchmark.clickhouse.com/#eyJzeXN0ZW0iOnsiQXRoZW5hIC...