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

infoschema: place INFORMATION_SCHEMA in new virtual table framework #13696

Merged
merged 3 commits into from
Nov 22, 2019
Merged

infoschema: place INFORMATION_SCHEMA in new virtual table framework #13696

merged 3 commits into from
Nov 22, 2019

Conversation

lonng
Copy link
Contributor

@lonng lonng commented Nov 22, 2019

Signed-off-by: Lonng heng@lonng.org

What problem does this PR solve?

Fix issue #13694

The informaction_schema should be placed in the new virtual table framework. See:

// TODO: Update INFORMATION_SCHEMA schema to use virtual table.

What is changed and how it works?

Refactor it.

Check List

Tests

  • Unit test

Release note

  • No need.

@lonng lonng added the type/enhancement The issue or PR belongs to an enhancement. label Nov 22, 2019
@codecov
Copy link

codecov bot commented Nov 22, 2019

Codecov Report

Merging #13696 into master will not change coverage.
The diff coverage is n/a.

@@             Coverage Diff             @@
##             master     #13696   +/-   ##
===========================================
  Coverage   79.9919%   79.9919%           
===========================================
  Files           473        473           
  Lines        116373     116373           
===========================================
  Hits          93089      93089           
  Misses        15938      15938           
  Partials       7346       7346

infoschema/tables.go Outdated Show resolved Hide resolved
Copy link
Member

@bb7133 bb7133 left a comment

Choose a reason for hiding this comment

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

LGTM

Copy link
Contributor

@crazycs520 crazycs520 left a comment

Choose a reason for hiding this comment

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

LGTM

@crazycs520
Copy link
Contributor

/run-all-tests

@crazycs520 crazycs520 added the status/LGT2 Indicates that a PR has LGTM 2. label Nov 22, 2019
@ngaut ngaut merged commit 153a6fa into pingcap:master Nov 22, 2019
@lonng lonng deleted the refactor-memtable branch November 22, 2019 09:49
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
status/LGT2 Indicates that a PR has LGTM 2. type/enhancement The issue or PR belongs to an enhancement.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants