TiDB: Exclude INFORMATION_SCHEMA

[shunki-fujita]

What type of PR is this?

• Bug Fix

Description

#7347
INFORMATION_SCHEMA is excluded in TiDB.

How is this tested?

• Unit tests (pytest, jest)
• E2E Tests (Cypress)
• Manually
• N/A

before change

• MySQL

mysql> SELECT col.table_schema as table_schema,
    ->                col.table_name as table_name,
    ->                col.column_name as column_name
    ->         FROM `information_schema`.`columns` col
    ->         WHERE col.table_schema NOT IN ('information_schema', 'performance_schema', 'mysql', 'sys');
+--------------+------------+-------------+
| table_schema | table_name | column_name |
+--------------+------------+-------------+
| test         | t1         | x           |
+--------------+------------+-------------+
1 row in set (0.00 sec)

• TiDB

mysql> SELECT col.table_schema as table_schema,
    ->                col.table_name as table_name,
    ->                col.column_name as column_name
    ->         FROM `information_schema`.`columns` col
    ->         WHERE col.table_schema NOT IN ('information_schema', 'performance_schema', 'mysql', 'sys');
+--------------------+---------------------------------------+-------------------------------------------+
| table_schema       | table_name                            | column_name                               |
+--------------------+---------------------------------------+-------------------------------------------+
| INFORMATION_SCHEMA | CLUSTER_DEADLOCKS                     | INSTANCE                                  |
| INFORMATION_SCHEMA | CLUSTER_DEADLOCKS                     | DEADLOCK_ID                               |
| INFORMATION_SCHEMA | CLUSTER_DEADLOCKS                     | OCCUR_TIME                                |
| INFORMATION_SCHEMA | CLUSTER_DEADLOCKS                     | RETRYABLE                                 |
...
| INFORMATION_SCHEMA | SEQUENCES                             | MIN_VALUE                                 |
| INFORMATION_SCHEMA | SEQUENCES                             | START                                     |
| INFORMATION_SCHEMA | SEQUENCES                             | COMMENT                                   |
| test               | t1                                    | x                                         |
+--------------------+---------------------------------------+-------------------------------------------+
1525 rows in set (0.02 sec)

after change

• MySQL

mysql> SELECT col.table_schema as table_schema,
    ->                col.table_name as table_name,
    ->                col.column_name as column_name
    ->         FROM `information_schema`.`columns` col
    ->         WHERE LOWER(col.table_schema) NOT IN ('information_schema', 'performance_schema', 'mysql', 'sys');
+--------------+------------+-------------+
| table_schema | table_name | column_name |
+--------------+------------+-------------+
| test         | t1         | x           |
+--------------+------------+-------------+
1 row in set (0.00 sec)

• TiDB

mysql> SELECT col.table_schema as table_schema,
    ->                col.table_name as table_name,
    ->                col.column_name as column_name
    ->         FROM `information_schema`.`columns` col
    ->         WHERE LOWER(col.table_schema) NOT IN ('information_schema', 'performance_schema', 'mysql', 'sys');
+--------------+------------+-------------+
| table_schema | table_name | column_name |
+--------------+------------+-------------+
| test         | t1         | x           |
+--------------+------------+-------------+
1 row in set (0.01 sec)

mysql>

Related Tickets & Documents

Mobile & Desktop Screenshots/Recordings (if there are UI changes)

[snickerjp]

LGTM

Since we have already discussed this in issue #7347, I have reviewed it and everything looks good.

[snickerjp]

@shunki-fujita

Thank you for your contribution!