Details
-
Bug
-
Status: Open (View Workflow)
-
Minor
-
Resolution: Unresolved
-
11.0.2, 10.5.22
-
None
-
None
Description
Specifing the charset utf8mb4 will throw later an unrelated error
DROP TABLE keyword; |
|
|
CREATE TABLE `keyword` ( |
`id` bigint(20) unsigned NOT NULL AUTO_INCREMENT, |
`search` varchar(255) NOT NULL, |
PRIMARY KEY (`id`), |
UNIQUE KEY `search` (`search`) |
|
|
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4; |
|
|
|
|
ALTER TABLE `keyword` ENGINE='ROCKSDB'; |
Using instead utf8mb3 it works fine.
Instead this is ok
DROP TABLE keyword; |
|
|
CREATE TABLE `keyword` ( |
`id` bigint(20) unsigned NOT NULL AUTO_INCREMENT, |
`search` varchar(255) NOT NULL, |
PRIMARY KEY (`id`) |
|
|
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4; |
|
|
|
|
ALTER TABLE `keyword` ENGINE='ROCKSDB'; |
ALTER TABLE `keyword` ADD KEY `search` (`search`); |
And finally is setting a UNIQUE, if fails again
DROP TABLE keyword; |
|
|
CREATE TABLE `keyword` ( |
`id` bigint(20) unsigned NOT NULL AUTO_INCREMENT, |
`search` varchar(255) NOT NULL, |
PRIMARY KEY (`id`) |
|
|
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4; |
|
|
ALTER TABLE `keyword` ENGINE='ROCKSDB'; |
ALTER TABLE `keyword` ADD UNIQUE KEY `search` (`search`); |