1.5.0.20251127

Important

Please make sure to update your ClickHouse version to 24.11 or newer to get the most out this version.

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

1.4.4.20251018 BETA

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.

1.4.3.20250807

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.

1.4.2.20250618

Bug Fixes

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

1.4.1.20250523

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.

1.3.4.20250417 BETA

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.

1.3.3.20250317

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

1.3.2.20250227 BETA

This release attempts to address the [HY000] I/O error: Bad address error and possibly the [HY000] Incomplete input stream error in Power BI. However, since we have not been able to reproduce these errors in our environment, we are releasing this as a beta to gather feedback from users experiencing the issues.

Note: This is not a final fix but an effort to further diagnose the problem.

Only the Windows version of the driver is included in this release, as the error occur only on Windows, and the fix modifies Windows-specific code.

1.3.1.20250213

Improvements

• Added support for query parameters in function calls (#467)

Bug Fixes

• Fixed issues with the locate function (#469)
• Resolved Power BI filter error (#462)

1.3.0.20241018

Improvements

• The driver is now built as a self-contained shared library (@alesapin) - see #428 for more details.

Breaking changes

• The driver no longer sets an autogenerated session_id to each request, as that could cause SESSION_IS_LOCKED errors. However, it is still possible to set a pre-defined session_id parameter via the Url DSN option. (@slvrtrn, #457)