MySQL错误“Specified key was too long; max key length is 100_MySQL
程序员文章站
2022-05-03 15:01:34
...
bitsCN.com
经过查询才知道,是Mysql的字段设置的太长了,于是我把这两个字段的长度改了一下就好了。
建立索引时,数据库计算key的长度是累加所有Index用到的字段的char长度后再按下面比例乘起来不能超过限定的key长度1000:
latin1 = 1 byte = 1 character
uft8 = 3 byte = 1 character
gbk = 2 byte = 1 character
举例能看得更明白些,以GBK为例:
CREATE UNIQUE INDEX `unique_record` ON reports (`report_name`, `report_client`, `report_city`);
其中report_name varchar(200), report_client varchar(200), report_city varchar(200)
(200 + 200 +200) * 2 = 1200 > 1000,所有就会报1071错误,只要将report_city改为varchar(100)那么索引就能成功建立。
如果表是UTF8字符集,那索引还是建立不了。bitsCN.com
建立索引时,数据库计算key的长度是累加所有Index用到的字段的char长度后再按下面比例乘起来不能超过限定的key长度1000:
latin1 = 1 byte = 1 character
uft8 = 3 byte = 1 character
gbk = 2 byte = 1 character
举例能看得更明白些,以GBK为例:
CREATE UNIQUE INDEX `unique_record` ON reports (`report_name`, `report_client`, `report_city`);
其中report_name varchar(200), report_client varchar(200), report_city varchar(200)
(200 + 200 +200) * 2 = 1200 > 1000,所有就会报1071错误,只要将report_city改为varchar(100)那么索引就能成功建立。
如果表是UTF8字符集,那索引还是建立不了。bitsCN.com
推荐阅读
-
ERROR 1071 (42000): Specified key was too long; max key length is 767 bytes
-
peewee.InternalError: (1071, 'Specified key was too long; max key length is 1000 bytes')
-
Specified key was too long max key length is 1000 bytes
-
ERROR 1071 (42000): Specified key was too long; max key length is 767 bytes
-
MySQL错误“Specified key was too long; max key length is 100
-
peewee.InternalError: (1071, 'Specified key was too long; max key length is 1000 bytes')
-
MySQL错误“Specified key was too long; max key length is 100_MySQL
-
laravel migrate时报错:Syntax error or access violation: 1071 Specified key was too long; max key length is 767 bytes
-
mysql建库时提示Specified key was too long max key length is_MySQL
-
MySQL:Specified key was too long; max key length is 767 bytes.