Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Fixed
-
10.2(EOL), 10.3(EOL), 10.4(EOL), 10.5, 10.6, 10.7(EOL), 10.8(EOL)
-
None
Description
CREATE OR REPLACE TABLE t1 (a CHAR(10) COLLATE DEFAULT) CHARACTER SET utf8mb4 COLLATE utf8mb4_bin; |
SHOW CREATE TABLE t1; |
+-------+---------------------------------------------------------------------------------------------------------------------------------+
|
| Table | Create Table |
|
+-------+---------------------------------------------------------------------------------------------------------------------------------+
|
| t1 | CREATE TABLE `t1` (
|
`a` char(10) COLLATE utf8mb4_bin DEFAULT NULL
|
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_bin |
|
+-------+---------------------------------------------------------------------------------------------------------------------------------+
|
Looks wrong. The expected behaviour would be to create the column with the collation utf8mb4_general_ci, i.e. use the default collation of the column character set utf8mb4, which is inherited from the table level.
It should not inherit the collation from the table level.
Attachments
Issue Links
- relates to
-
MDEV-27009 Add UCA-14.0.0 collations
- Closed
-
MDEV-27690 Crash on `CHARACTER SET csname COLLATE DEFAULT` in column definition
- Closed
-
MDEV-27782 Wrong columns when using table level `CHARACTER SET utf8mb4 COLLATE DEFAULT`
- Closed
-
MDEV-28067 Multiple conflicting column COLLATE clauses are not rejected
- Closed
-
MDEV-27743 Remove Lex::charset
- Closed