-
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 a bug that create two views with same name success (#58770) #59058
ddl: fix a bug that create two views with same name success (#58770) #59058
Conversation
Signed-off-by: ti-chi-bot <ti-community-prow-bot@tidb.io>
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: D3Hunter, tiancaiamao 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 |
[LGTM Timeline notifier]Timeline:
|
/retest |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## release-6.5 #59058 +/- ##
================================================
Coverage ? 73.6401%
================================================
Files ? 1097
Lines ? 353177
Branches ? 0
================================================
Hits ? 260080
Misses ? 76370
Partials ? 16727 |
This is an automated cherry-pick of #58770
What problem does this PR solve?
Issue Number: close #58769
Problem Summary:
What changed and how does it work?
After one 'create view' ddl job delivered (queuing), the another
create view
ddl job come.The check for table name duplicated is incorrect.
When old table exists and there is no
or replace
, it should report error.Check List
Tests
Side effects
Documentation
Release note
Please refer to Release Notes Language Style Guide to write a quality release note.