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

add clustered/nonclustered keyword in normal index should report error #23390

Closed
lysu opened this issue Mar 18, 2021 · 2 comments
Closed

add clustered/nonclustered keyword in normal index should report error #23390

lysu opened this issue Mar 18, 2021 · 2 comments
Labels
type/bug The issue is confirmed as a bug.

Comments

@lysu
Copy link
Contributor

lysu commented Mar 18, 2021

Bug Report

Please answer these questions before submitting your issue. Thanks!

1. Minimal reproduce step (Required)

create table tbl_0 ( col_0 decimal not null , col_1 blob(207) , col_2 text , col_3 datetime default '1986-07-01' , col_4 bigint unsigned default 1504335725690712365 , primary key idx_0 ( col_3,col_2(1),col_1(6) ) , key idx_1 ( col_3 ) clustered)

2. What did you expect to see? (Required)

should report error, because we don't support it in 5.0

3. What did you see instead (Required)

create table success.

4. What is your TiDB version? (Required)

master

@lysu lysu added the type/bug The issue is confirmed as a bug. label Mar 18, 2021
@lysu
Copy link
Contributor Author

lysu commented Mar 18, 2021

fixed by #23270

@lysu lysu closed this as completed Mar 18, 2021
@ti-srebot
Copy link
Contributor

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

6. Fixed versions

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

No branches or pull requests

2 participants