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.
| scheme | resolved | example | |
|---|---|---|---|
EXPECTED_ENGINE_VERSION | chdb-core | at compile time | 26.7.0 |
engine_version | chdb-core | by the linked library | 26.7.0 |
clickhouse_version | ClickHouse | by a query | 26.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.