[MDEV-25508] SHOW CREATE TABLE does not consistently display ignored index status Created: 2021-04-24  Updated: 2021-04-24  Resolved: 2021-04-24

Status: Closed
Project: MariaDB Server
Component/s: N/A
Affects Version/s: 10.6.0
Fix Version/s: N/A

Type: Bug Priority: Major
Reporter: Ian Gilfillan Assignee: Unassigned
Resolution: Not a Bug Votes: 0
Labels: need_feedback
Environment:


 Description   

 
CREATE OR REPLACE TABLE t1 (id INT PRIMARY KEY, b INT, KEY k1(b) IGNORED);
 
SHOW INDEXES FROM t1\G
*************************** 1. row ***************************
        Table: t1
   Non_unique: 0
     Key_name: PRIMARY
 Seq_in_index: 1
  Column_name: id
    Collation: A
  Cardinality: 0
     Sub_part: NULL
       Packed: NULL
         Null: 
   Index_type: BTREE
      Comment: 
Index_comment: 
      Ignored: NO
*************************** 2. row ***************************
        Table: t1
   Non_unique: 1
     Key_name: k1
 Seq_in_index: 1
  Column_name: b
    Collation: A
  Cardinality: 0
     Sub_part: NULL
       Packed: NULL
         Null: YES
   Index_type: BTREE
      Comment: 
Index_comment: 
      Ignored: YES
 
SHOW CREATE TABLE t1;
+-------+-------------------------------------------------------------------------------------------------------------------+
| Table | Create Table                                                                                                      |
+-------+-------------------------------------------------------------------------------------------------------------------+
| t1    | CREATE TABLE "t1" (
  "id" int(11) NOT NULL,
  "b" int(11) DEFAULT NULL,
  PRIMARY KEY ("id"),
  KEY "k1" ("b")
) |
+-------+-------------------------------------------------------------------------------------------------------------------+

This doesn't appear to affect all environments - I tested this with http://hasky.askmonty.org/archive/10.6/build-39581/kvm-bintar-trusty-amd64/



 Comments   
Comment by Elena Stepanova [ 2021-04-24 ]

It looks like you have sql_mode set to (at least) NO_KEY_OPTIONS and NO_TABLE_OPTIONS. Could it be?

Comment by Elena Stepanova [ 2021-04-24 ]

or sql_mode=ORACLE, for example.

Comment by Ian Gilfillan [ 2021-04-24 ]

I had Oracle mode active. Works in default SQL_MODE.

Comment by Elena Stepanova [ 2021-04-24 ]

It's meant to be so for ORACLE mode, as it sets NO_KEY_OPTIONS.

Generated at Thu Feb 08 09:38:14 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.