Skip to main content

Module version

Module version 

Source
Expand description

Which engine this build carries.

Three accessors, each reporting exactly one versioning scheme. Nothing here falls back to another scheme when its own source is unavailable: a chdb-core release number and a ClickHouse version number cannot be compared, so answering one question with the other number is worse than answering with an error.

schemeresolvedexample
EXPECTED_ENGINE_VERSIONchdb-coreat compile time26.7.0
engine_versionchdb-coreby the linked library26.7.0
clickhouse_versionClickHouseby a query26.5.1.1

A chdb-core release number is not a ClickHouse one: X.Y is the ClickHouse minor line the release sits on and Z is chdb-core’s own counter, so the two agree on the first two fields at most.

Constants§

ENGINE_SOURCE
Where the linked library came from, as the build script resolved it.
EXPECTED_ENGINE_VERSION
The chdb-core release this build fetched, without the leading v.

Functions§

clickhouse_version
The ClickHouse version the linked engine reports, as SELECT version() gives it.
engine_version
The chdb-core release the linked library reports, without the leading v.