-
Notifications
You must be signed in to change notification settings - Fork 5.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
errno: move the error code from the parser/mysql to tidb/errno #15277
Conversation
/run-all-tests |
/run-all-tests |
/run-all-tests |
/run-all-tests |
Codecov Report
@@ Coverage Diff @@
## master #15277 +/- ##
===========================================
Coverage 80.4680% 80.4680%
===========================================
Files 503 503
Lines 133970 133970
===========================================
Hits 107803 107803
Misses 17736 17736
Partials 8431 8431 |
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
/run-all-tests
Not really... I mean the code compatibility, if we remove the parser exported function, the cherry-pick work would be trouble. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
/merge |
/run-all-tests |
@tiancaiamao merge failed. |
/rebuild |
Signed-off-by: sre-bot <sre-bot@pingcap.com>
cherry pick to release-3.0 in PR #15283 |
What problem does this PR solve?
Some times we need to define/modify the error code.
The error code is defined in the parser repo, so we need to update two repositories in a single PR, that's cumbersome.
I want to move the TiDB customed error back to the TiDB repo.
What is changed and how it works?
The error code is now defined in github/pingcap/tidb/errno
I have a PR to verify TiDB doesn't depend on parser/mysql errors anymore (it's not important to merge the PR or not).
From now on, don't add more error code to parser/mysql error definitions, use tidb/errno instead.
(We can choose to clean the parser repo or not)
Check List
Tests
Code changes
Side effects
Breaking backward compatibilityRelated changes
It's better to cherry-pick it to reduce conflict in the future.