v1.6.0

1.6.0 (2026-02-27)

Features

• adding swift 6.2, 6.1 and 6.0 for CI (#17) (b535d1d)

v1.5.1

1.5.1 (2025-10-23)

Bug Fixes

• CI again.... (6963bfe)
• Sendable warnings (#13) (52eda1e)
• Turning ExceptionMessage public and conforms to Equatable (#15) (4bb1034)

v1.5.0

1.5.0 (2025-04-10)

Features

• Adding support for Maps where keys and values are Strings (#11) (fdbe981)

Bug Fixes

• CI (aca8add)
• CI test (91a1af4)
• CI tests (3e50cbd)
• tests for CI (0ba466d)

v1.4.2

1.4.2 (2024-09-26)

Bug Fixes

• Add CI release automation (7dd14be)

1.4.1 Fix DateTime with TimeZone

What's Changed

• FIx DateTime with TimeZone by @planetMDX in #9

Full Changelog: 1.4.0...1.4.1

1.4.0 Additional datatypes

What's Changed

• Support for more ClickHouse-Types by @planetMDX in #8

New Contributors

• @planetMDX made their first contribution in #8

Full Changelog: 1.3.0...1.4.0

1.3.0 Nullable

This feature release adds support for Nullable datatype

1.2.0 Timeouts

This release adds timeouts to make ClickHouseNIO more reliable in production environments.

While running ClickHouseNIO we discovered various edge cases where a connection could get stuck. These events are infrequent (once every 2 weeks), but result in annoying deadlocks.

Because networks unreliable by nature, ClickHouseNIO uses different timeouts to prevent potential deadlocks while waiting for a server response. All timeouts can be controlled via ClickHouseConfiguration and use default values as shown below:

let config = try ClickHouseConfiguration(
    hostname: "localhost", 
    ...,
    connectTimeout: .seconds(10),
    readTimeout: .seconds(90),
    queryTimeout: .seconds(600))
,

All timeouts will close the connection. Different timeouts trigger different exceptions:

• connectTimeout will throw NIO.ChannelError.connectTimeout(TimeAmount) if the connection to the ClickHouse server cannot be establised after this period of time.
• readTimeout: If a query is running, and the ClickHouseNIO client does not receive any network package, the conncection is closed and throws ClickHouseError.readTimeout. This can happen, if the network connection is interrupted while waiting for a response. Usually, even while waiting for a query result, packages are exchanged very frequently.
• queryTimeout is the total time after a query will be terminated and the connection is closed. Because ClickHouseNIO is also capable of queueing queries, this includes the time in the queue as well. On a very busy server, a long waiting time starts to close connections. If a connection is closed, all queries in the queue will return a failed future with the exception ClickHouseError.queryTimeout.

Timeouts can also be specified for a single query with connection.command(sql: sql, timeout: .seconds(30)), but keep in mind that this also includes queue time.

1.1.2 Fix insert + select statements

Fixed a bug with the combination of insert & select statements like INSERT INTO db.table SELECT * FROM db2.table2 which triggered an assertion on non production builds

1.1.1 UUID coding bugfix

ixed:

• Bug #2 ClickHouse uses little endian encoding for UUIDs