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

tidb 4.0.0 can not show view data_type #22316

Closed
xqwbx163 opened this issue Jan 9, 2021 · 5 comments · Fixed by #22363
Closed

tidb 4.0.0 can not show view data_type #22316

xqwbx163 opened this issue Jan 9, 2021 · 5 comments · Fixed by #22363
Assignees
Labels
component/executor severity/minor type/bug The issue is confirmed as a bug.

Comments

@xqwbx163
Copy link

xqwbx163 commented Jan 9, 2021

image
create view xxx as select * from xxx;
then show column data_type ,select * from INFORMATION_SCHEMA.columns where table_name=‘v_t_store_refund_info’
the data_type column value is "unspecified"

Release Version: v4.0.0
Edition: Community
Git Commit Hash: 689a6b6
Git Branch: heads/refs/tags/v4.0.0
UTC Build Time: 2020-05-28 01:37:40
GoVersion: go1.13
Race Enabled: false
TiKV Min Version: v3.0.0-60965b006877ca7234adaced7890d7b029ed1306
Check Table Before Drop: false

@xqwbx163 xqwbx163 added the type/bug The issue is confirmed as a bug. label Jan 9, 2021
@beihaiguaishou
Copy link
Contributor

/pick-up

@ti-challenge-bot
Copy link

It is not a pickable issue!

Details

Tip : If you want this issue to be picked, you need to add a challenge-program label to it.

Warning: None

@beihaiguaishou
Copy link
Contributor

/assign

beihaiguaishou added a commit to beihaiguaishou/tidb that referenced this issue Jan 12, 2021
beihaiguaishou added a commit to beihaiguaishou/tidb that referenced this issue Jan 12, 2021
beihaiguaishou added a commit to beihaiguaishou/tidb that referenced this issue Jan 12, 2021
@ti-srebot
Copy link
Contributor

ti-srebot commented Jan 12, 2021

Please edit this comment or add a new comment to complete the following information

Not a bug

  1. Remove the 'type/bug' label
  2. Add notes to indicate why it is not a bug

Duplicate bug

  1. Add the 'type/duplicate' label
  2. Add the link to the original bug

Bug

Note: Make Sure that 'component', and 'severity' labels are added
Example for how to fill out the template: #20100

1. Root Cause Analysis (RCA) (optional)

2. Symptom (optional)

3. All Trigger Conditions (optional)

4. Workaround (optional)

5. Affected versions

[v3.0.0:v3.0.20],[v4.0.0:v4.0.10],[v5.0.0-rc]

6. Fixed versions

master

@ti-srebot
Copy link
Contributor

( component or sig(label) ) fields are empty.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
component/executor severity/minor type/bug The issue is confirmed as a bug.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants