Skip to content

Upgrade chdb to v26.3.0#36

Merged
wudidapaopao merged 2 commits into
chdb-io:mainfrom
wudidapaopao:upgrade-chdb-version
May 20, 2026
Merged

Upgrade chdb to v26.3.0#36
wudidapaopao merged 2 commits into
chdb-io:mainfrom
wudidapaopao:upgrade-chdb-version

Conversation

@wudidapaopao
Copy link
Copy Markdown
Contributor

@wudidapaopao wudidapaopao commented May 20, 2026

Upgrade libchdb to v26.3.0 (based on ClickHouse 26.3) from chdb-io/chdb-core.

Closes #35

- Switch download source to chdb-io/chdb-core repository
- Bump package version to 1.7.0
chDB v26 forbids invoking the legacy CLI entry point (query_stable_v2)
more than once per process and rejects mixing it with chdb_connect.
Route the standalone query/queryBind paths through a lazily-initialized
shared in-memory chdb_connection and inject queryBind parameters via
prepended "SET param_xxx = '...'" statements. Session.queryBind continues
to throw and unused QuerySession helpers are removed.

Also fix a long-standing strftime bug that emitted trailing garbage for
Date parameters and bump the package to 2.0.0 since standalone query()
calls now share state across invocations.
@wudidapaopao wudidapaopao mentioned this pull request May 20, 2026
@wudidapaopao wudidapaopao merged commit 76f2f91 into chdb-io:main May 20, 2026
7 checks passed
Comment thread update_libchdb.sh
# Get the newest release version
# LATEST_RELEASE=$(curl --silent "https://api.github.com/repos/chdb-io/chdb/releases/latest" | grep '"tag_name":' | sed -E 's/.*"([^"]+)".*/\1/')
LATEST_RELEASE=v3.7.2
LATEST_RELEASE=v26.3.0
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Wait before this was on v3?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, chdb was split into chdb and chdb-core before. Hence chdb-core has its independent version number aligned with that of ClickHouse, which leads to this sudden version number jump.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

CH 26.x version

2 participants