2.0.0.262

• BREAKING removed support for TSV/JSON drivers, will only use binary now
• BREAKING enabled compression by default in all connections. If you pass a HttpClient to connection constructor, make sure it is configured to perform decompression (or use Compression=false in connection string)
• Added support for reading raw result as returned by ClickHouse (ExecuteRawResultAsync)
• Improved Decimal performance
• Improved cancellation mechanics
• Refactoring of serialization internals, for better performance in some cases
• Parameters will correctly use InvariantCulture where relevant
• Improved Tuple/Nullable support in parameters
• Added support for writing Nested values using BulkCopy (see wiki)

1.3.0.243

• Fixed bug with small-value negative decimals writing (#33)
• Added protocol to connection string (#30) (@Treno1)

1.2.0.230

• Added support for query parameters (see ClickHouse parameters syntax) (@Treno1 )
  • basic Dapper queries are now supported
• Added DbConnectionFactory
• Added support for backticked columns in BulkCopy
• Fixed: CreateParameter will not add parameter to Command by default (was not consistent with other ADO.NET providers)

1.1.1.204

• Fixed handling of Nullable types in JSON and TSV drivers #24
• Fixed exception in connection constructor when passing a HttpClient #23
• Improved schema handling: will return more specific Decimal type instead of Decimal(x,y) #20

1.1.0.197

• New: connection string parameter: SessionId to set session ID manually if needed
• Fix: ClickHouseDataAdapter.Fill exception when dataset contains Nullable field
• Fix: ClickHouseBulkCopy exception when inserting subset of columns
• Fix: Array type fields will now be returned as <type>[] instead of object[], to match GetFieldType returned value

1.0.0

• Removed double from DateTime64 arithmetic, only integers are now used in calculations
• Enabled compression for Bulk insertion always (increased performance)
• Added GetDateTimeOffset method for ClickHouseDataReader class for better timezone handling
• DateTimeKind.Local/DateTimeKind.Unspecified are now used meaningfully