Details
-
Bug
-
Status: Closed (View Workflow)
-
Critical
-
Resolution: Fixed
-
10.5, 10.6, 10.2(EOL), 10.3(EOL), 10.4(EOL), 10.7(EOL), 10.8(EOL)
-
None
Description
These statements crash the server:
CREATE OR REPLACE TABLE t1 (a CHAR(10) CHARACTER SET latin1 COLLATE DEFAULT); |
CREATE OR REPLACE TABLE t1 (a CHAR(10) CHARACTER SET utf8mb4 COLLATE DEFAULT); |
Note, this statements do not:
CREATE OR REPLACE TABLE t1 (a CHAR(10)) CHARACTER SET utf8mb4 COLLATE DEFAULT; |
CREATE OR REPLACE TABLE t1 (a CHAR(10)) CHARACTER SET latin1 COLLATE DEFAULT; |
But they can produce a wrong table. See MDEV-27782.
Attachments
Issue Links
- relates to
-
MDEV-27009 Add UCA-14.0.0 collations
- Closed
-
MDEV-27782 Wrong columns when using table level `CHARACTER SET utf8mb4 COLLATE DEFAULT`
- Closed
-
MDEV-27743 Remove Lex::charset
- Closed
-
MDEV-27853 Wrong data type on column `COLLATE DEFAULT` and table `COLLATE some_non_default_collation`
- Closed
-
MDEV-28067 Multiple conflicting column COLLATE clauses are not rejected
- Closed