Breaking Change: Constructor signature change breaks LinqToDB compatibility

[concertdictate]

Version: 0.7.19 Issue: Breaking change in ClickHouseConnection constructor

Description
The constructor signature for ClickHouseConnection was changed in version 0.7.19 from:
ClickHouseConnection(string connectionString)
to:
ClickHouseConnection(string connectionString, bool parameter)

This breaking change affects LinqToDB integration, as LinqToDB expects the single-parameter constructor and fails with:
LinqToDB.LinqToDBException: Constructor not found in target type: ClickHouse.Driver.ADO.ClickHouseConnection..ctor(String)

Impact
LinqToDB users cannot upgrade to ClickHouse.Driver 0.7.19+
Forces downgrade to 0.7.18 to maintain compatibility
Breaks existing integrations that rely on the previous constructor signature

Reproduction

var opt = new DataOptions()
    .UseClickHouse(ClickHouseProvider.ClickHouseDriver)
    .UseConnectionString(connectionString);

  await using var db = new DataConnection(opt);
        var result = await db.ExecuteAsync<string>("SELECT version()");

Suggestion
Consider maintaining backward compatibility by:

Keeping the single-parameter constructor overload
Documenting this as a breaking change in release notes
Environment
ClickHouse.Driver: 0.7.19
LinqToDB: RC3
Framework: .NET
This affects any ORM or library that dynamically creates ClickHouseConnection instances using reflection with the string-only constructor.

[MaceWindu]

yep, .ctor(string) on connection class is de-facto standard for ADO.NET providers

[MaceWindu]

@concertdictate as workaround you can use connection factory with DataOptions

[SpencerTorres]

Is this related to #10?

@dorki any thoughts?

Perhaps we can just add another constructor as you suggested

[SpencerTorres]

We may also need to update Linq2DB as mentioned in #12

[dorki]

Yes i can push a fix later today to bring back the old ctor sig as well. Sorry for that.

[dorki]

#16

[SpencerTorres]

Released 0.7.20 with original constructor present