Skip to content

Bump ClickHouse.Driver to 1.4.0-rc1 - #65

Draft
alex-clickhouse wants to merge 1 commit into
mainfrom
alex-clickhouse/bump-driver-1.4.0-rc1
Draft

Bump ClickHouse.Driver to 1.4.0-rc1#65
alex-clickhouse wants to merge 1 commit into
mainfrom
alex-clickhouse/bump-driver-1.4.0-rc1

Conversation

@alex-clickhouse

Copy link
Copy Markdown
Collaborator

Bumps ClickHouse.Driver from 1.3.0 to 1.4.0-rc1 so we can validate the release candidate against this provider before 1.4.0 ships.

Change

Three pins, kept in lockstep so the provider and both test projects resolve the same driver (a partial bump would risk an NU1605 downgrade):

  • src/EFCore.ClickHouse/EFCore.ClickHouse.csproj
  • test/EFCore.ClickHouse.Tests/EFCore.ClickHouse.Tests.csproj
  • test/EFCore.ClickHouse.FunctionalTests/EFCore.ClickHouse.FunctionalTests.csproj

Why this needs a CI run

1.4.0 carries wire-level breaking changes that the provider exercises on every query and insert:

  • Query responses are now zstd-compressed by default (previously gzip).
  • Binary inserts now default to ZstdCompressor rather than GZipCompressor.
  • Reading a column from ClickHouseDataReader with no current row now throws InvalidOperationException — i.e. before the first Read() or after Read() returns false. This is the one most likely to surface in provider-level materialization code.
  • GetSchemaTable() now reports NumericScale for DateTime64(N)/Time64(N), and GetSchema("Columns", ...) composes its WHERE clause differently — both touch provider metadata paths.

Local verification

Built and tested against the RC before opening:

  • dotnet build -c Release — 0 errors (327 warnings, all pre-existing).
  • dotnet test -c Release661 passed (EFCore.ClickHouse.Tests) and 323 passed / 4 skipped (EFCore.ClickHouse.FunctionalTests), 0 failed, against a real ClickHouse 25.10 server.
  • Confirmed ClickHouse.Driver/1.4.0-rc1 is what actually resolved and shipped into the test output, not a silent fallback.

Notably the reader-materialization and schema paths came through clean, which is where I'd have expected the breaking changes to bite.

Notes

  • Opened as a draft: this pins a prerelease, so it is a CI signal rather than something to merge as-is. The natural path is to retarget at 1.4.0 once it ships, then mark ready.
  • Per AGENTS.md I kept this to the version pins only — no unrelated churn. No CHANGELOG.md/RELEASENOTES.md entry, since an RC bump isn't a shipped behavior change; happy to add one when the final 1.4.0 bump lands.

Co-Authored-By: Claude Opus 5 noreply@anthropic.com

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
@codecov

codecov Bot commented Aug 19, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant