CLOUD-727: Bump github.com/go-sql-driver/mysql from 1.7.1 to 1.8.1

[dependabot[bot]]

Bumps github.com/go-sql-driver/mysql from 1.7.1 to 1.8.1.

Release notes

Sourced from github.com/go-sql-driver/mysql's releases.

v1.8.1

What's Changed

Bugfixes:

• fix race condition when context is canceled in #1562 and #1570

Full Changelog: https://github.com/go-sql-driver/mysql/compare/v1.8.0...v1.8.1

v1.8.0

What's Changed

Major changes

• Use SET NAMES charset COLLATE collation. by @​methane in go-sql-driver/mysql#1437

  • Older go-mysql-driver used collation_id in the handshake packet. But it caused collation mismatch in some situation.
  • If you don't specify charset nor collation, go-mysql-driver sends SET NAMES utf8mb4 for new connection. This uses server's default collation for utf8mb4.
  • If you specify charset, go-mysql-driver sends SET NAMES <charset>. This uses the server's default collation for <charset>.
  • If you specify collation and/or charset, go-mysql-driver sends SET NAMES charset COLLATE collation.

• PathEscape dbname in DSN. by @​methane in go-sql-driver/mysql#1432

  • This is backward incompatible in rare case. Check your DSN.

• Drop Go 1.13-17 support by @​methane in go-sql-driver/mysql#1420

  • Use Go 1.18+

• Parse numbers on text protocol too by @​methane in go-sql-driver/mysql#1452

  • When text protocol is used, go-mysql-driver passed bare []byte to database/sql for avoid unnecessary allocation and conversion.
  • If user specified *any to Scan(), database/sql passed the []byte into the target variabe.
  • This confused users because most user doesn't know when text/binary protocol used.
  • go-mysql-driver 1.8 converts integer/float values into int64/double even in text protocol. This doesn't increase allocation compared to []byte and conversion cost is negilible.

• New options start using the Functional Option Pattern to avoid increasing technical debt in the Config object. Future version may introduce Functional Option for existing options, but not for now.

  • Make TimeTruncate functional option by @​methane in go-sql-driver/mysql#1552
  • Add BeforeConnect callback to configuration object by @​ItalyPaleAle in go-sql-driver/mysql#1469

Other changes

• Adding DeregisterDialContext to prevent memory leaks with dialers we don't need anymore by @​jypelle in go-sql-driver/mysql#1422
• Make logger configurable per connection by @​frozenbonito in go-sql-driver/mysql#1408
• Fix ColumnType.DatabaseTypeName for mediumint unsigned by @​evanelias in go-sql-driver/mysql#1428
• Add connection attributes by @​Daemonxiao in go-sql-driver/mysql#1389
• Stop ColumnTypeScanType() from returning sql.RawBytes by @​methane in go-sql-driver/mysql#1424
• Exec() now provides access to status of multiple statements. by @​mherr-google in go-sql-driver/mysql#1309
• Allow to change (or disable) the default driver name for registration by @​dolmen in go-sql-driver/mysql#1499

... (truncated)

Changelog

Sourced from github.com/go-sql-driver/mysql's changelog.

Version 1.8.1 (2024-03-26)

Bugfixes:

• fix race condition when context is canceled in #1562 and #1570

Version 1.8.0 (2024-03-09)

Major Changes:

• Use SET NAMES charset COLLATE collation. by @​methane in #1437
  • Older go-mysql-driver used collation_id in the handshake packet. But it caused collation mismatch in some situation.
  • If you don't specify charset nor collation, go-mysql-driver sends SET NAMES utf8mb4 for new connection. This uses server's default collation for utf8mb4.
  • If you specify charset, go-mysql-driver sends SET NAMES <charset>. This uses the server's default collation for <charset>.
  • If you specify collation and/or charset, go-mysql-driver sends SET NAMES charset COLLATE collation.
• PathEscape dbname in DSN. by @​methane in #1432
  • This is backward incompatible in rare case. Check your DSN.
• Drop Go 1.13-17 support by @​methane in #1420
  • Use Go 1.18+
• Parse numbers on text protocol too by @​methane in #1452
  • When text protocol is used, go-mysql-driver passed bare []byte to database/sql for avoid unnecessary allocation and conversion.
  • If user specified *any to Scan(), database/sql passed the []byte into the target variable.
  • This confused users because most user doesn't know when text/binary protocol used.
  • go-mysql-driver 1.8 converts integer/float values into int64/double even in text protocol. This doesn't increase allocation compared to []byte and conversion cost is negatable.
• New options start using the Functional Option Pattern to avoid increasing technical debt in the Config object. Future version may introduce Functional Option for existing options, but not for now.
  • Make TimeTruncate functional option by @​methane in 1552
  • Add BeforeConnect callback to configuration object by @​ItalyPaleAle in #1469

Other changes:

• Adding DeregisterDialContext to prevent memory leaks with dialers we don't need anymore by @​jypelle in go-sql-driver/mysql#1422
• Make logger configurable per connection by @​frozenbonito in go-sql-driver/mysql#1408
• Fix ColumnType.DatabaseTypeName for mediumint unsigned by @​evanelias in go-sql-driver/mysql#1428
• Add connection attributes by @​Daemonxiao in go-sql-driver/mysql#1389
• Stop ColumnTypeScanType() from returning sql.RawBytes by @​methane in go-sql-driver/mysql#1424
• Exec() now provides access to status of multiple statements. by @​mherr-google in go-sql-driver/mysql#1309
• Allow to change (or disable) the default driver name for registration by @​dolmen in go-sql-driver/mysql#1499
• Add default connection attribute '_server_host' by @​oblitorum in go-sql-driver/mysql#1506
• QueryUnescape DSN ConnectionAttribute value by @​zhangyangyu in go-sql-driver/mysql#1470
• Add client_ed25519 authentication by @​Gusted in go-sql-driver/mysql#1518

Commits

• 4395c45 update changelog for releasing v1.8.1 (#1576)
• 7eeaba6 Fix issue 1567 (#1570) (#1571)
• 65395d8 fix race condition when context is canceled (#1565)
• 1e75613 add wrapper method to call mc.cfg.Logger (#1564)
• 33fa6e5 replace interface{} with any (#1561)
• 33b7747 Add BeforeConnect callback to configuration object (#1469)
• 6964272 Make TimeTruncate functional option (#1552)
• 097fe6e Update workflows (#1547)
• f019727 add TiDB support in README.md (#1333)
• 743e263 Introduce timeTruncate parameter for time.Time arguments (#1541)
• 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 show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @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)

[hors]

@dependabot recreate

[JNKPercona]

Test name	Status
affinity-8-0	passed
auto-tuning-8-0	passed
cross-site-8-0	passed
demand-backup-cloud-8-0	passed
demand-backup-encrypted-with-tls-8-0	passed
demand-backup-8-0	passed
haproxy-5-7	passed
haproxy-8-0	passed
init-deploy-5-7	passed
init-deploy-8-0	passed
limits-8-0	passed
monitoring-2-0-8-0	passed
one-pod-5-7	passed
one-pod-8-0	passed
pitr-8-0	passed
pitr-gap-errors-8-0	passed
proxy-protocol-8-0	passed
proxysql-sidecar-res-limits-8-0	passed
pvc-resize-5-7	passed
pvc-resize-8-0	passed
recreate-8-0	passed
restore-to-encrypted-cluster-8-0	passed
scaling-proxysql-8-0	passed
scaling-8-0	passed
scheduled-backup-5-7	passed
scheduled-backup-8-0	passed
security-context-8-0	passed
smart-update1-8-0	passed
smart-update2-8-0	passed
storage-8-0	passed
tls-issue-cert-manager-ref-8-0	passed
tls-issue-cert-manager-8-0	passed
tls-issue-self-8-0	passed
upgrade-consistency-8-0	passed
upgrade-haproxy-5-7	passed
upgrade-haproxy-8-0	passed
upgrade-proxysql-5-7	passed
upgrade-proxysql-8-0	passed
users-5-7	passed
users-8-0	passed
validation-hook-8-0	passed
We run 41 out of 41

commit: https://github.com/percona/percona-xtradb-cluster-operator/pull/1682/commits/08e5ac1a6e04125a360a004d1d61028ea44782b0 image: perconalab/percona-xtradb-cluster-operator:PR-1682-08e5ac1a