pingcap / pingcap/docs-cn

If the target table is a partition table, the HOW INDEXES FROM query cannot find information?

Open
#14,037 1 comment 0 reactions 1 assignee View on GitHub

@xzhangxian1008 is already working on this.

Since May 26, 2023.

Dominant language
Python
Stars
1.8k
Forks
1.2k
Avg merge
1d 16h
Merged PRs (30d)
31

Description

File: /release-6.5/sql-statements/sql-statement-show-indexes.md
show create table p\G;
*************************** 1. row ***************************
Table: p
Create Table: CREATE TABLE p (
id int(11) NOT NULL,
fname varchar(30) DEFAULT NULL,
lname varchar(30) DEFAULT NULL,
hired date NOT NULL DEFAULT '1970-01-01',
separated date DEFAULT '9999-12-31',
job_code int(11) DEFAULT NULL,
store_id int(11) NOT NULL
) ENGINE=InnoDB DEFAULT CHARSET=latin1 COLLATE=latin1_bin
PARTITION BY RANGE (store_id)
(PARTITION p0 VALUES LESS THAN (6),
PARTITION p1 VALUES LESS THAN (11),
PARTITION p2 VALUES LESS THAN (16),
PARTITION p3 VALUES LESS THAN (21))
1 row in set (0.00 sec)

SHOW INDEXES FROM p;
Empty set (0.00 sec)

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.