Multiple collations should fail creating table .

[ramanich1]

Bug Report

Please answer these questions before submitting your issue. Thanks!

1. Minimal reproduce step (Required)

drop table if exists t1;
CREATE TABLE t1 ( x VARCHAR(10)
  COLLATE ascii_bin
  COLLATE ascii_bin);

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

mysql> CREATE TABLE t1 ( x VARCHAR(10)
    ->   COLLATE ascii_bin
    ->   COLLATE ascii_bin);
ERROR 1064 (42000): Multiple COLLATE clauses near 'ascii_bin)' at line 3

3. What did you see instead (Required)

mysql> CREATE TABLE t1 ( x VARCHAR(10)
    ->   COLLATE ascii_bin
    ->   COLLATE ascii_bin);
Query OK, 0 rows affected (0.01 sec)

4. What is your TiDB version? (Required)

mysql> select version();
+-----------------------------------------------+
| version()                                     |
+-----------------------------------------------+
| 5.7.25-TiDB-v6.1.0-alpha-482-g81a852077-dirty |
+-----------------------------------------------+

[ramanich1]

Matches with mysql5.7

[bb7133]

/label type/compatiblity-mysql8

[ti-chi-bot]

@bb7133: The label(s) type/compatiblity-mysql8 cannot be applied. These labels are supported: challenge-program, compatibility-breaker, first-time-contributor, contribution, require-LGT3, good first issue, correctness, duplicate, proposal, security, needs-more-info, needs-cherry-pick-4.0, needs-cherry-pick-5.0, needs-cherry-pick-5.1, needs-cherry-pick-5.2, needs-cherry-pick-5.3, needs-cherry-pick-5.4, needs-cherry-pick-6.0, needs-cherry-pick-6.1, affects-4.0, affects-5.0, affects-5.1, affects-5.2, affects-5.3, affects-5.4, affects-6.0, affects-6.1, may-affects-4.0, may-affects-5.0, may-affects-5.1, may-affects-5.2, may-affects-5.3, may-affects-5.4, may-affects-6.0, may-affects-6.1.

In response to this:

/label type/compatiblity-mysql8

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the ti-community-infra/tichi repository.

[zimulala]

Matches with mysql5.7

This issue is not considered a bug because it is compatible with MySQL-5.7