This release fixes parameter binding when string values contain special characters such as newlines, tabs, or backslashes. It also corrects UTF-16 to/from UTF-8 conversion in the Unicode driver.

New features:

• Add support for the ClickHouse Time type

Fixed bugs:

• Parameters containing newlines, tabs, or backslashes could not be parsed by ClickHouse #551
• Use the correct class for UTF-16 to/from UTF-8 conversion #559

Full Changelog: v1.5.2.20260217...v1.5.3.20260311

This release introduces a new configuration option, SqlCompatibilitySettings. When enabled, it adjusts certain ClickHouse query settings to better align with standard SQL behavior. While it provides little benefit for user-written queries, it is important for queries generated by external tools such as Power BI, ensuring better compatibility with traditional databases.

You can read more about these settings on the ODBC Driver documentation page

The Power BI connector does not yet support this new setting, though an update is currently in progress. In the meantime, if you are installing the driver for use with Power BI, please download and install the -powerbi-win64 file, where SqlCompatibilitySettings is enabled by default.

New features:

• Compression is now enabled by default #541
• Missing scalar functions have now been implemented #549

Fixed bugs:

• Bool columns are represented as a string #486
• Power BI DirectQuery: ClickHouse fails to parse ODBC parameter placeholders in expressions #501
• Unknown expression or function identifier 'SQL_TSI_FRAC_SECOND' #513
• Power BI ODBC: ClickHouse throws 'CANNOT_INSERT_NULL_IN_ORDINARY_COLUMN' on Nullable Int/Decimal fields in DirectQuery mode #502
• Power BI Direct Query Cannot Aggregate Nullable Columns #488

Full Changelog: 1.5.1.20251201...v1.5.2.20260217

In this version, compression is enabled by default so it can be tested with Power BI, where this option is not configurable.

Full Changelog: v1.5.0.20251127...1.5.1.20251201

What's Changed

• The build includes the changes from 1.4.4.20251018 BETA, specifically an updated network stack that should reduce the Incomplete Input Stream errors (#419).
• As a result of updating the network stack, the certificate validation error (#443) has also been fixed.
• The driver now supports loading longs strings in parts using SQLGetData.
• The new version of the driver now supports compression (#103). This option is currently disabled by default, but we plan to enable it after gathering enough feedback from our users. Because compression is not enabled by default, and the Power BI adapter does not allow changing driver configuration parameters, compression will not initially be enabled for Power BI. This will change once compression becomes enabled by default.

Special thanks to @ilejn for providing the initial implementation for the compression support.

Full Changelog: 1.4.3.20250807...v1.5.0.20251127

This beta version introduces significant changes under the hood. In general, its goal is to improve error handling for issues that occur while reading data from the server to the client. These fixes should address errors such as Incomplete input stream, particularly when the error is caused by networking issues or when ClickHouse raises an error while sending data. While such errors might not always be preventable, the goal is to display an informative message explaining why the error occurred.

Since these changes significantly affect how network traffic is handled, we are first releasing a public beta to gather community feedback. We especially recommend trying this release if you frequently encounter the Incomplete input stream error.

New Features

• #518 Added Query ID to error messages. This is especially helpful for debugging the #419: Incomplete input stream bug, as it helps locate the corresponding query in system.query_log.
• #520 Added a ClientName parameter to the driver configuration. This parameter will be included in the User-Agent header of each request to ClickHouse, fixes #459.

Bug Fixes

• Fix filter in Power BI for non-Latin characters (#449)

This version includes the changes from 1.3.4.20250417 BETA, specifically in how the new driver reports data to client applications. It also adds details about supported types that were missing in previous versions of the driver.

Additionally, the driver includes several fixes and improvements:

• Allow tilde (~) in passwords
• Implement SQLGetInfo(SQL_DBMV_VER) to get the version of the ClickHouse Server
• Fixes Int64 columns are loaded as binary columns in PowerBI

Note: Power BI caches data definitions. This means that even if you update the driver and try to load a table previously accessed with the older driver, Power BI may still use the data definitions it received from the older version. To prevent issues such as numeric columns being recognized as binary data, you need to reload the table definitions by clicking the small reload button in the upper-right corner. See #445 (comment) for details.

This beta version introduces significant changes under the hood. Specifically, we add more detailed information about supported data types that the driver shares with client applications. Instead of using general types such as VARCHAR or INTEGER, we now report the actual ClickHouse types and their properties. The change itself does not significantly affect visible behavior, and as far as we are aware, it only fixes one issue: Int64 columns are loaded as binary columns in PowerBI. However, it paves the way for future improvements that were not possible without this change.

Knowing that we cannot foresee how other applications rely on the way the driver reports the supported types, we are first releasing a beta version to collect feedback.

Technical details:

• The SQLGetTypeInfo function now returns native ClickHouse types, as advertised in the documentation. Specifically, instead of using TINYINT, SMALLINT, INT, REAL, TEXT, TIMESTAMP, etc., it now returns Int8, Int16, Int32, Float, String, DateTime64.
• Many columns of the SQLGetTypeInfo function have been populated with relevant data, where previously they contained NULLs or simple placeholders.
• Similar to SQLGetTypeInfo, SQLColumns now also returns native type names and is populated with data that was previously missing.
• DateTime64 now comes first when requesting type information for SQL_TYPE_TIMESTAMP. This allows using fractions of a second in the WHERE clause and is also compatible with DateTime as long as the fraction of a second is set to zero.

• Fixes [HY000] I/O error: Bad address error and [HY000] Incomplete input stream errors (#446, #419, #339)