-
Notifications
You must be signed in to change notification settings - Fork 5.9k
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
ddl: fix the wrong logic to assert whether table has foreign key #51808
ddl: fix the wrong logic to assert whether table has foreign key #51808
Conversation
Signed-off-by: Yang Keao <[email protected]>
Codecov Report
Additional details and impacted files@@ Coverage Diff @@
## master #51808 +/- ##
================================================
+ Coverage 70.7345% 72.8173% +2.0827%
================================================
Files 1476 1476
Lines 437888 437926 +38
================================================
+ Hits 309738 318886 +9148
+ Misses 108742 98980 -9762
- Partials 19408 20060 +652
Flags with carried forward coverage won't be shown. Click here to find out more.
|
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
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: bb7133, ywqzzy The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Signed-off-by: ti-chi-bot <[email protected]>
Signed-off-by: ti-chi-bot <[email protected]>
In response to a cherrypick label: new pull request created to branch |
In response to a cherrypick label: new pull request created to branch |
In response to a cherrypick label: new pull request created to branch |
Signed-off-by: ti-chi-bot <[email protected]>
What problem does this PR solve?
Issue Number: close #51807, close #51762
Problem Summary:
If the foreign key is an empty slice, the condition
nt.ForeignKeys != nil
will meet. It would be better to assert it withlen(nt.ForeignKeys) > 0
What changed and how does it work?
Change
nt.ForeignKeys != nil
tolen(nt.ForeignKeys) > 0
.Actually, I wonder whether there are other similar issues in TiDB. It's very likely to have bugs in similar pattern 🤔 .
Check List
Tests
Side effects
Documentation
Release note