mysql, errno: Unify the mysql error codes and related error messages.

[wddevries]

What problem does this PR solve?

Issue Number: close #29026

Problem Summary:

There are two copies of most error codes and error messages.

What changed and how does it work?

This pull request:

• moves the struct mysql.ErrMessage to pkg/errno/errname.go
• moves the function mysql.Message to pkg/errno/errname.go
• adds any missing error codes from pkg/parser/mysql/errcode.go to pkg/errno/errcode.go
• updates all references to error codes defined in pkg/parser/mysql/errcode.go to the versions defined in pkg/errno/errcode.go
• removes the file pkg/parser/mysql/errcode.go
• adds any missing error messages from pkg/parser/mysql/errname.go to pkg/errno/errname.go
• updates all references to the messages in pkg/parser/mysql/errname.go to the versions in pkg/errno/errname.go
• removes the file pkg/parser/mysql/errname.go.

The error messages in both the mysql package and errno were compared to insure compatibility.

Check List

Tests

• Unit test
• Integration test
• Manual test (add detailed scripts or steps below)
• No need to test

  • I checked and no code files have been changed.

Side effects

• Performance regression: Consumes more CPU
• Performance regression: Consumes more Memory
• Breaking backward compatibility

Documentation

• Affects user behaviors
• Contains syntax changes
• Contains variable changes
• Contains experimental features
• Changes MySQL compatibility

Release note

Please refer to Release Notes Language Style Guide to write a quality release note.

None

[tiprow]

Hi @wddevries. Thanks for your PR.

PRs from untrusted users cannot be marked as trusted with /ok-to-test in this repo meaning untrusted PR authors can never trigger tests themselves. Collaborators can still trigger tests on the PR using /test all.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[codecov]

Codecov Report

Attention: Patch coverage is 74.19355% with 8 lines in your changes missing coverage. Please review.

Project coverage is 74.7454%. Comparing base (6f49d25) to head (e2d5931).

❗ Current head e2d5931 differs from pull request most recent head 4c904df

Please upload reports for the commit 4c904df to get more accurate results.

Additional details and impacted files

@@               Coverage Diff                @@
##             master     #58790        +/-   ##
================================================
+ Coverage   72.9110%   74.7454%   +1.8343%     
================================================
  Files          1699       1722        +23     
  Lines        469738     472516      +2778     
================================================
+ Hits         342491     353184     +10693     
+ Misses       106116      97068      -9048     
- Partials      21131      22264      +1133     

Flag	Coverage Δ
integration	48.5050% <23.0769%> (?)
unit	72.3479% <74.1935%> (+0.2293%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

Components	Coverage Δ
dumpling	52.6910% <ø> (ø)
parser	∅ <ø> (∅)
br	60.9596% <0.0000%> (+16.0760%)	⬆️

[ti-chi-bot]

@wddevries: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
pull-lightning-integration-test	e2d5931	link	true	/test pull-lightning-integration-test
pull-br-integration-test	e2d5931	link	true	/test pull-br-integration-test

Full PR test history. Your PR dashboard.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign benjamin2037, d3hunter, fixdb, zanmato1984 for approval, ensuring that each of them provides their approval before proceeding. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• OWNERS
• pkg/ddl/OWNERS
• pkg/domain/OWNERS
• pkg/executor/importer/OWNERS
• pkg/expression/OWNERS
• pkg/lightning/OWNERS
• pkg/meta/OWNERS
• pkg/parser/OWNERS
• pkg/statistics/OWNERS
• pkg/tablecodec/OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment