[orthoxerox]

No, I haven't, but it looks like it's a standalone console application, while DuckDB is in-process, like SQLite, and lives inside its JDBC driver. This means I can use it inside any compatible GUI and get stuff like schema browsing and IntelliSense out of the box. Since I have DBeaver open all day anyway, DuckDB is always a tab away.

[wenc]

Clickhouse local is very fast and good for many purposes but DuckDB is equally fast (or faster in some cases but this is a moving target) and supports a wider range of SQL that people like me often use.

DuckDB is great for data scientists and people who need to run complex analytic queries in their Jupyter notebooks and their Python prod code on local or S3 hosted data.

[benjaminwootton]

What’s the workflow with JDBC? Say you connect Tableau to it. How would you populate it with data?

[orthoxerox]

My workflow is that I have a connection to c:\temp\scratchpad.db in DBeaver that I populate via

  create table some_data as select * from 'c:\temp\whatever.csv'

or

  create table other_data as select * from read_parquet('c:\temp\000000_0')

which I then can transform using SQL and export the result into CSV, Parquet or SQLite when needed.