v1.1.0

• ClickHouse 25.1 serializes booleans as 1/0 when using FORMAT JSON. We only used that in introspection. Change it to use toJSONString instead.
• Fix returning explain query plan

v1.0.5

• Fix a bug where starting in clickhouse 24.7, users would get default values for the given data type instead of real results. #32

v1.0.4

• Implement PrintSchemaAndCapabilities command. Enables the ddn CLI to perform introspection without needing to start an instance of the connector, which makes introspection faster. Note the DDN CLI does not yet implement this.
• Bug fix: scalar aggregates may return other scalars, creating dependencies. Fix schema response not including those scalar type dependencies

v1.0.3

• Update SDK version to enable unauthorized access to health endpoint

v1.0.2

• Allow DateTime64 shorthand for DateTime64(3)
• Allow Decimal shorthand for Decimal(10, 0)
• Make datatypes case insensitive
• When introspection returns no columns (parameterized view issue), preserve any manually written columns
• Correct support for casting from JSON Objects paramters to named Tuples, and JSON Arrays to anonymous tuples
• Fix printing tuples in bound parameters

v1.0.1

• Bug fix: remove erroneous group by and order by clauses in foreach queries. Remote relationships should now function as expected. The previous fix was incorrect.

v1.0.0

• Stable Release

v0.2.11

• Bugfix: add missing group by clause for foreach queries. This should fix remote relationships.

v0.2.10

• Correct CLI implementation of Init command (used to behave the same as update)
• Update sdk & errors
• Fix version returned by capabilities
• Fix parameter escaping, enabling complex data types as parameters
• Remove deprecated JSON data type, see clickhouse docs

v0.2.9

• Change namespaceing to use . separator instead of _. We assume table names are less likely to contain periods, so this reduces likelyhood of naming conflicts.This will change generated type names and will thus manifest as a breaking change for some users
• Support Nested column types correctly, (previously these were treated as essentially Tuple columns)
• Support subfield selection on complex column types.
• Add support for relationships on column subfields, if the path to the subfield does not include lists
• Fix datatype parser: add ability to parse SimpleAggregateFunction and AggregateFunction columns