ddl: fix the wrong logic to assert whether table has foreign key (#51808) #51821
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Signed-off-by: ti-chi-bot <[email protected]>
ti-chi-bot
added
release-note-none
13 tasks
ti-chi-bot
bot
added
do-not-merge/cherry-pick-not-approved
size/XXL
Codecov Report
Additional details and impacted files@@ Coverage Diff @@
## release-7.1 #51821 +/- ##
================================================
Coverage ? 73.4474%
================================================
Files ? 1212
Lines ? 379733
Branches ? 0
================================================
Hits ? 278904
Misses ? 83020
Partials ? 17809 |
ti-chi-bot
bot
added
size/S
ti-chi-bot
bot
added
needs-1-more-lgtm
|
/lgtm |
ti-chi-bot
bot
added
lgtm
and removed
needs-1-more-lgtm
ti-chi-bot
added
the
cherry-pick-approved
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: bb7133, YangKeao, 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 |
|
/retest |
Signed-off-by: YangKeao <[email protected]>
YangKeao
force-pushed
the
cherry-pick-51808-to-release-7.1
branch
from
1f7c4a8
to
4057b69
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is an automated cherry-pick of #51808
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 != nilwill meet. It would be better to assert it withlen(nt.ForeignKeys) > 0What changed and how does it work?
Change
nt.ForeignKeys != niltolen(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