query gets wrong result, related to order and information_schema table

[wjhuang2016]

Bug Report

Please answer these questions before submitting your issue. Thanks!

1. Minimal reproduce step (Required)

mysql> SELECT character_set_name, id, sortlen FROM information_schema.collations ORDER BY collation_name, id;
+--------------------+------+---------+
| character_set_name | id   | sortlen |
+--------------------+------+---------+
| ascii              |   65 |       1 |
| binary             |   63 |       1 |
| gbk                |   87 |       1 |
| gbk                |   28 |       1 |
| latin1             |   47 |       1 |
| utf8               |   83 |       1 |
| utf8               |   33 |       1 |
| utf8               |  192 |       1 |
| utf8mb4            |   46 |       1 |
| utf8mb4            |   45 |       1 |
| utf8mb4            |  224 |       1 |
+--------------------+------+---------+
11 rows in set (0.00 sec)

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

Order by id

3. What did you see instead (Required)

Wrong

4. What is your TiDB version? (Required)

master

[Defined2014]

The behavior is same as MySQL. Maybe it's not a bug, because it's order by collation_name. @wjhuang2016

mysql> SELECT character_set_name, id, sortlen FROM information_schema.collations ORDER BY collation_name, id;
...
| utf8               |  83 |       1 |
| utf8               | 213 |       8 |
| utf8               | 202 |       8 |
| utf8               | 203 |       8 |
| utf8               | 209 |       8 |
| utf8               | 198 |       8 |
| utf8               |  33 |       1 |
| utf8               | 223 |       1 |
| utf8               | 212 |       8 |
| utf8               | 210 |       8 |
| utf8               | 193 |       8 |
| utf8               | 194 |       8 |
| utf8               | 204 |       8 |
| utf8               | 208 |       8 |
| utf8               | 197 |       8 |
| utf8               | 195 |       8 |
| utf8               | 207 |       8 |
| utf8               | 211 |       8 |
| utf8               | 205 |       8 |
| utf8               | 196 |       8 |
| utf8               | 206 |       8 |
| utf8               | 199 |       8 |
| utf8               | 200 |       8 |
| utf8               |  76 |       1 |
| utf8               | 201 |       8 |
| utf8               | 214 |       8 |
| utf8               | 192 |       8 |
| utf8               | 215 |       8 |
+--------------------+-----+---------+

[bb7133]

I don't think this issue is worth fixing, since the behavior is the same as MySQL and it doesn't matter for the users actually.

[github-actions]

Please check whether the issue should be labeled with 'affects-x.y' or 'fixes-x.y.z', and then remove 'needs-more-info' label.