Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
db_verify::getIndex()
: Support index_col_name
optional parts
In the MariaDB `CREATE TABLE` [`index_definition`](https://mariadb.com/kb/en/create-table/#index-definitions), the `index_col_name` could have an optional length and a sort order: ``` index_definition: {INDEX|KEY} [index_name] [index_type] (index_col_name,...) [index_option] ... {{{|}}} {FULLTEXT|SPATIAL} [INDEX|KEY] [index_name] (index_col_name,...) [index_option] ... {{{|}}} [CONSTRAINT [symbol]] PRIMARY KEY [index_type] (index_col_name,...) [index_option] ... {{{|}}} [CONSTRAINT [symbol]] UNIQUE [INDEX|KEY] [index_name] [index_type] (index_col_name,...) [index_option] ... {{{|}}} [CONSTRAINT [symbol]] FOREIGN KEY [index_name] (index_col_name,...) reference_definition index_col_name: col_name [(length)] [ASC | DESC] index_type: USING {BTREE | HASH | RTREE} index_option: [ KEY_BLOCK_SIZE [=] value {{{|}}} index_type {{{|}}} WITH PARSER parser_name {{{|}}} COMMENT 'string' {{{|}}} CLUSTERING={YES| NO} ] [ IGNORED | NOT IGNORED ] reference_definition: REFERENCES tbl_name (index_col_name,...) [MATCH FULL | MATCH PARTIAL | MATCH SIMPLE] [ON DELETE reference_option] [ON UPDATE reference_option] reference_option: RESTRICT | CASCADE | SET NULL | NO ACTION ``` `db_verify::getIndex()` didn't handle this possibility, leading to a database validity check failure despite the index actually existing. Fixes: #5054
- Loading branch information