Skip to content
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 db charset modification panic in an uppercase schema #19286

Merged
merged 4 commits into from
Aug 19, 2020

Conversation

tangenta
Copy link
Contributor

What problem does this PR solve?

Issue Number: close #19273

Problem Summary:
The database name should be changed to lower case before passing it into copySchemaTables.

What is changed and how it works?

What's Changed: Omitted.

How it Works: Omitted.

Related changes

  • Need to cherry-pick to the release branch

Check List

Tests

  • Unit test
  • Integration test

Side effects

N/A

Release note

  • Fix a schema charset modification panic bug in an uppercase schema.

@tangenta tangenta added the sig/sql-infra SIG: SQL Infra label Aug 19, 2020
Copy link
Contributor

@AilinKid AilinKid left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@ti-srebot ti-srebot added the status/LGT1 Indicates that a PR has LGTM 1. label Aug 19, 2020
Copy link
Member

@wjhuang2016 wjhuang2016 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@ti-srebot ti-srebot removed the status/LGT1 Indicates that a PR has LGTM 1. label Aug 19, 2020
ti-srebot
ti-srebot previously approved these changes Aug 19, 2020
@ti-srebot ti-srebot added the status/LGT2 Indicates that a PR has LGTM 2. label Aug 19, 2020
ddl/db_integration_test.go Outdated Show resolved Hide resolved
@bb7133 bb7133 added require-LGT3 Indicates that the PR requires three LGTM. needs-cherry-pick-3.0 labels Aug 19, 2020
@bb7133
Copy link
Member

bb7133 commented Aug 19, 2020

LGTM

@ti-srebot ti-srebot removed the status/LGT2 Indicates that a PR has LGTM 2. label Aug 19, 2020
@ti-srebot ti-srebot added the status/LGT3 The PR has already had 3 LGTM. label Aug 19, 2020
@bb7133
Copy link
Member

bb7133 commented Aug 19, 2020

/merge

@ti-srebot ti-srebot added the status/can-merge Indicates a PR has been approved by a committer. label Aug 19, 2020
@ti-srebot
Copy link
Contributor

/run-all-tests

@ti-srebot
Copy link
Contributor

@tangenta merge failed.

@bb7133
Copy link
Member

bb7133 commented Aug 19, 2020

/run-integration-ddl-test
/run-sqllogic-test

@bb7133 bb7133 closed this Aug 19, 2020
@bb7133 bb7133 reopened this Aug 19, 2020
@glorv
Copy link
Contributor

glorv commented Aug 19, 2020

/run-check_dev

1 similar comment
@glorv
Copy link
Contributor

glorv commented Aug 19, 2020

/run-check_dev

@bb7133 bb7133 merged commit d464a27 into pingcap:master Aug 19, 2020
ti-srebot pushed a commit to ti-srebot/tidb that referenced this pull request Aug 19, 2020
@ti-srebot
Copy link
Contributor

cherry pick to release-3.0 in PR #19301

ti-srebot pushed a commit to ti-srebot/tidb that referenced this pull request Aug 19, 2020
@ti-srebot
Copy link
Contributor

cherry pick to release-4.0 in PR #19302

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
require-LGT3 Indicates that the PR requires three LGTM. sig/sql-infra SIG: SQL Infra status/can-merge Indicates a PR has been approved by a committer. status/LGT3 The PR has already had 3 LGTM.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

infoschema: panic occurred when applying default charset modification for databases named in uppercase.
6 participants