#DuckDB v1.1.3 is ready and so is the latest #chSQL with a new release introducing 20+ new #ClicKHouse macros/fixes, `ch_scan()` w/ multiple formats & much more!
Instantly available for @duckdb.org through the Community Extensions repository! It's #QuackScience!

duckdb.org/community_ex...

It's 2025 and we're bored so the time is perfect to implement a native binary client for the @duckdb.org #DuckDB ClickHouse Native extension for chsql 🚸 alternative to the HTTP/S based client. We're racing the clickhouse-cpp and clickhouse-rs Extensions side by side for fun and #quackscience 🔥

Duck migrations are one of nature's most fascinating phenomena and now you can be part of one too with chsql: A #DuckDB Community Extension for #ClickHouse data refu-geese 🦆🦆 🚫 ||||- 90% smaller 50% faster for any language/platform/architecture and ready to fly anytime 🚀

#OLAP #DuckDB #NotYandex

Migrating from Clickhouse to #DuckDB and got SQL query muscle memory? The #chsql extension provides 100+ ClickHouse Macros and Functions for @duckdb.org to keep your house going without the clicks and clouds! Perfect anywhere for in-process, serverless and serverful usage!

It's #quackscience 🦆🧪

Hard to tell who but something or someone seems to be using our chsql #DuckDB community extension a lot 🎉 hopefully its something good rather than the opposite - does anyone know what "it" might be?

A bunch of ClickHouse tools expect and use the system table to discover databases, tables, types and so on. So here's yet another DuckDB chsql extension to emulate a very basic Clickhouse system table feeding from DuckDB meta, but open to implement disk, process and memory usage details... ⚙️

🚀 The latest chsql_native version is now available on the community extensions repository: duckdb.org/community_ex...

Thanks @samansmink.bsky.social for the holiday PR merge!

That's right! DuckDB Quackscience "chsql" provides ClickHouse Macros, "chsql_native" provides native format reading and "http_server" provides a ClickHouse compatible HTTP API + Play UI github.com/quackscience

It wasn't a fluke and the mystery continues on... how's #chsql almost up to the avro extension? Who's using it? We're burning to find out 😅

Oh yeah! We already have an WIP ingestion/merge interface on top of parquet files/buckets (instead of Mergetree tables) with distributed reads and a dedicated low-mem parquet merge function in chsql already 👍

Introducing #httpserver: a #DuckDB Community Extension adding a tiny #HTTP #API + User Interface to any DuckDB instance to query and be queried without any wrappers.

Works in pair with the #chsql #flock function to allow distributed queries to dynamic DuckDB workers pools

#QuackScience 🦆🧪

🎉 New Community Extension: chsql (1.0.6) https://duckdb.org/community_extensions/extensions/chsql.html

The ingestion part is still only available in quackpipe where its being experimented with while the read parquet "mergetree" is already part of the chsql repository: github.com/quackscience...

If dbvis supports ClickHouse HTTP connections (no clue if that's the case as the docs are unclear) you can try with the DuckDB http_server + chsql Comminity Extensions which emulated a basic CH HTTP API

🚀 It's ready! The first version of the emulated clickhouse system table functionality (and a couple more things) has been merged into mainline `chsql` and queued for release on the community repository for release! This should make lots of existing CH integrations work out of the box 🎉