chore(deps): bump github.com/ClickHouse/clickhouse-go/v2 from 2.0.14 to 2.6.0

[dependabot]

Bumps github.com/ClickHouse/clickhouse-go/v2 from 2.0.14 to 2.6.0.

Release notes

Sourced from github.com/ClickHouse/clickhouse-go/v2's releases.

v2.6.0, 2023-01-27

New features

• Client info specification implementation #876 by @​jkaflik

Bug fixes

• Better handling for broken connection errors in the std interface #879 by @​n-oden

Chore

• Document way to provide table or database identifier with query parameters #875 by @​jkaflik
• Bump github.com/ClickHouse/ch-go from 0.51.0 to 0.51.2 #881

v2.5.1

Bug fixes

• Flag connection as closed on broken pipe #871 by @​n-oden

v2.5.0

New features

• Buffered compression column by column for a native protocol. Introduces the MaxCompressionBuffer option - max size (bytes) of compression buffer during column-by-column compression (default 10MiB) #808 by @​gingerwizard and @​jkaflik
• Support custom types that implement sql.Scanner interface (e.g. type customString string) #850 by @​DarkDrim
• Append query options to the context instead of overwriting #860 by @​aaron276h
• Query parameters support #854 by @​jkaflik
• Expose DialStrategy function to the user for custom connection routing. #855 by @​jkaflik

Bug fixes

• Close connection on Cancel. This is to make sure context timed out/canceled connection is not reused further #764 by @​gingerwizard
• Fully parse secure and skip_verify in DSN query parameters. #862 by @​n-oden

Chore

• Added tests covering read-only user queries #837 by @​jkaflik
• Agreed on a batch append fail semantics #853 by @​jkaflik

v2.4.3

Bug Fixes

• Fix in batch concurrency - batch could panic if used in separate go routines.

The issue was originally detected due to the use of a batch in a go routine and Abort being called after the connection was released on the batch. This would invalidate the connection which had been subsequently reassigned.

This issue could occur as soon as the conn is released (this can happen in a number of places e.g. after Send or an Append error), and it potentially returns to the pool for use in another go routine. Subsequent releases could then occur e.g., the user calls Abort mainly but also Send would do it. The result is the connection being closed in the release function while another batch or query potentially used it.

This release includes a guard to prevent release from being called more than once on a batch. It assumes that batches are not thread-safe - they aren't (only connections are).

v2.4.2

... (truncated)

Changelog

Sourced from github.com/ClickHouse/clickhouse-go/v2's changelog.

2.6.0, 2023-01-27

New features

• Client info specification implementation #876 by @​jkaflik

Bug fixes

• Better handling for broken connection errors in the std interface #879 by @​n-oden

Chore

• Document way to provide table or database identifier with query parameters #875 by @​jkaflik
• Bump github.com/ClickHouse/ch-go from 0.51.0 to 0.51.2 #881

2.5.1, 2023-01-10

Bug fixes

• Flag connection as closed on broken pipe #871 by @​n-oden

2.5.0, 2023-01-10

New features

• Buffered compression column by column for a native protocol. Introduces the MaxCompressionBuffer option - max size (bytes) of compression buffer during column-by-column compression (default 10MiB) #808 by @​gingerwizard and @​jkaflik
• Support custom types that implement sql.Scanner interface (e.g. type customString string) #850 by @​DarkDrim
• Append query options to the context instead of overwriting #860 by @​aaron276h
• Query parameters support #854 by @​jkaflik
• Expose DialStrategy function to the user for custom connection routing. #855 by @​jkaflik

Bug fixes

• Close connection on Cancel. This is to make sure context timed out/canceled connection is not reused further #764 by @​gingerwizard
• Fully parse secure and skip_verify in DSN query parameters. #862 by @​n-oden

Chore

• Added tests covering read-only user queries #837 by @​jkaflik
• Agreed on a batch append fail semantics #853 by @​jkaflik

2.4.3, 2022-11-30

Bug Fixes

• Fix in batch concurrency - batch could panic if used in separate go routines. The issue was originally detected due to the use of a batch in a go routine and Abort being called after the connection was released on the batch. This would invalidate the connection which had been subsequently reassigned. This issue could occur as soon as the conn is released (this can happen in a number of places e.g. after Send or an Append error), and it potentially returns to the pool for use in another go routine. Subsequent releases could then occur e.g., the user calls Abort mainly but also Send would do it. The result is the connection being closed in the release function while another batch or query potentially used it. This release includes a guard to prevent release from being called more than once on a batch. It assumes that batches are not thread-safe - they aren't (only connections are).

2.4.2, 2022-11-24

Bug Fixes

• Don't panic on Send() on batch after invalid Append. #830

... (truncated)

Commits

• b2f9409 2.6.0 changelog
• 409f6cd Bump github.com/ClickHouse/ch-go from 0.51.0 to 0.51.2 (#881)
• 1be6c11 Better handling for connection errors in the std interface (#879)
• d8d8124 Document way to provide table or database identifier with query parameters (#...
• 61b30f3 Client info specification implementation (#876)
• 0c79b0f changelog 2.5.1
• 936a983 Handle EPIPE errors (#871)
• 930a6c9 chore: v2.5.0 CHANGELOG.md
• bcb27bb Bump github.com/paulmach/orb from 0.7.1 to 0.8.0 (#866)
• 197b589 Expose DialStrategy function to user for custom connection routing (#855)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[dependabot]

Superseded by #33.