索引长度过长 ERROR 1071 (42000): Specified key was too long; max key length is 767 bytes
1.发现问题
今天在修改innodb表的某个列的长度时,报如下错误:
- alter table test2 modify column id varchar(500);
- ERROR 1071 (42000): Specified key was too long; max key length is 767 bytes
alter table test2 modify column id varchar(500);
ERROR 1071 (42000): Specified key was too long; max key length is 767 bytes
2.分析问题
2.1 问题原因分析
其实从上面的报错中我们已经能看是因为索引达到长度限制,所以报错。查看id列是否有索引:
- mysql> show index from test2\G;
- *************************** 1. row ***************************
- Table: test2
- Non_unique: 1
- Key_name: id
- Seq_in_index: 1
- Column_name: id
- Collation: A
- Cardinality: 0
- Sub_part: NULL
- Packed: NULL
- Null: YES
- Index_type: BTREE
- Comment:
- Index_comment:
- 1 row in set (0.00 sec)
mysql> show index from test2\G;
*************************** 1. row ***************************
Table: test2
Non_unique: 1
Key_name: id
Seq_in_index: 1
Column_name: id
Collation: A
Cardinality: 0
Sub_part: NULL
Packed: NULL
Null: YES
Index_type: BTREE
Comment:
Index_comment:
1 row in set (0.00 sec)
##删除id列的索引后, alter table test2 modify操作可以正常执行
2.2 关于mysql索引长度限制
1)单列索引长度限制
- From the manual at http://dev.mysql.com/doc/refman/5.6/en/create-table.html >>从5.6的官方文档中我们能找到如下双引号中解释
- "For CHAR, VARCHAR, BINARY, and VARBINARY columns, indexes can be created that use only the leading part of column values, using col_name(length) syntax to specify an index prefix length.
- ...
- Prefixes can be up to 1000 bytes long (767 bytes for InnoDB tables). Note that prefix limits are measured in bytes, whereas the prefix length in CREATE TABLE statements is interpreted as number of characters ...">>>对于myisam和innodb存储引擎,prefixes的长度限制分别为1000 bytes和767 bytes。注意prefix的单位是bytes,但是建表时我们指定的长度单位是字符。
- A utf8 character can use up to 3 bytes. Hence you cannot index columns or prefixes of columns longer than 333 (MyISAM) or 255 (InnoDB) utf8 characters. >>以utf8字符集为例,一个字符占3个bytes。因此在utf8字符集下,对myisam和innodb存储引擎创建索引的单列长度不能超过333个字符和255个字符
From the manual at http://dev.mysql.com/doc/refman/5.6/en/create-table.html >>从5.6的官方文档中我们能找到如下双引号中解释
"For CHAR, VARCHAR, BINARY, and VARBINARY columns, indexes can be created that use only the leading part of column values, using col_name(length) syntax to specify an index prefix length.
...
Prefixes can be up to 1000 bytes long (767 bytes for InnoDB tables). Note that prefix limits are measured in bytes, whereas the prefix length in CREATE TABLE statements is interpreted as number of characters ...">>>对于myisam和innodb存储引擎,prefixes的长度限制分别为1000 bytes和767 bytes。注意prefix的单位是bytes,但是建表时我们指定的长度单位是字符。 A utf8 character can use up to 3 bytes. Hence you cannot index columns or prefixes of columns longer than 333 (MyISAM) or 255 (InnoDB) utf8 characters. >>以utf8字符集为例,一个字符占3个bytes。因此在utf8字符集下,对myisam和innodb存储引擎创建索引的单列长度不能超过333个字符和255个字符
- create table test2(id varchar(256),primary key(id));
- ERROR 1071 (42000): Specified key was too long; max key length is 767 bytes
create table test2(id varchar(256),primary key(id));
ERROR 1071 (42000): Specified key was too long; max key length is 767 bytes
##对于innodb表,索引列长度大于255时,会报错。
从上面可以看出,mysql 在创建单列索引的时候对列的长度是有限制的 myisam和innodb存储引擎下长度限制分别为1000 bytes和767 bytes。(注意bytes和character的区别)
2) 组合索引长度限制
对于innodb存储引擎,多列索引的长度限制如下:
每个列的长度不能大于767 bytes;所有组成索引列的长度和不能大于3072 bytes
参考如下例子(下面默认使用的使用innodb存储引擎,smallint 占2个bytes,timestamp占4个bytes,utf8字符集。utf8字符集下,一个character占三个byte)
- mysql> create table test3(id varchar(255),key(id));
- Query OK, 0 rows affected (0.11 sec) >>索引列长度小于767(255*3=765),表创建成功
- mysql> drop table test3;
- Query OK, 0 rows affected (0.03 sec)
- mysql> create table test3(id varchar(256),key(id)); >>索引列长度大于767(256*3=768),所以创建表失败
- ERROR 1071 (42000): Specified key was too long; max key length is 767 bytes
- mysql> create table test3 (id varchar(255),name varchar(255),name1 varchar(255),name2 varchar(255),name3 varchar(5),key (id,name,name1,name2,name3)); >>innodb下多列索引,所有列长度和大于3072/3=1024 (255*4+5=1025),所以表创建失败
- ERROR 1071 (42000): Specified key was too long; max key length is 3072 bytes
- mysql> create table test3 (id varchar(255),name varchar(255),name1 varchar(255),name2 varchar(255),name3 varchar(4),key (id,name,name1,name2,name3)); >>
- Query OK, 0 rows affected (0.09 sec)
mysql> create table test3(id varchar(255),key(id));
Query OK, 0 rows affected (0.11 sec) >>索引列长度小于767(255*3=765),表创建成功 mysql> drop table test3;
Query OK, 0 rows affected (0.03 sec) mysql> create table test3(id varchar(256),key(id)); >>索引列长度大于767(256*3=768),所以创建表失败
ERROR 1071 (42000): Specified key was too long; max key length is 767 bytes
mysql> create table test3 (id varchar(255),name varchar(255),name1 varchar(255),name2 varchar(255),name3 varchar(5),key (id,name,name1,name2,name3)); >>innodb下多列索引,所有列长度和大于3072/3=1024 (255*4+5=1025),所以表创建失败
ERROR 1071 (42000): Specified key was too long; max key length is 3072 bytes
mysql> create table test3 (id varchar(255),name varchar(255),name1 varchar(255),name2 varchar(255),name3 varchar(4),key (id,name,name1,name2,name3)); >>
Query OK, 0 rows affected (0.09 sec)
对于myisam存储引擎,多列索引长度限制如下:
每个列的长度不能大于1000 bytes,所有组成索引列的长度和不能大于1000 bytes
例子如下
- mysql> create table test3(id varchar(334),key(id)) engine=myisam; >>索引列长度大于1000 bytes (334*3=1002),建表报错
- ERROR 1071 (42000): Specified key was too long; max key length is 1000 bytes
- mysql> create table test3(id varchar(333),key(id)) engine=myisam; >>索引列长度小于1000 bytes (333*3=999),建表成功
- Query OK, 0 rows affected (0.07 sec)
- mysql> create table test3(id varchar(300),name varchar(34),key(id,name)) engine=myisam; >>多列索引,所有列长度大于1000 bytes 建表报错
- ERROR 1071 (42000): Specified key was too long; max key length is 1000 bytes
- mysql>
mysql> create table test3(id varchar(334),key(id)) engine=myisam; >>索引列长度大于1000 bytes (334*3=1002),建表报错
ERROR 1071 (42000): Specified key was too long; max key length is 1000 bytes
mysql> create table test3(id varchar(333),key(id)) engine=myisam; >>索引列长度小于1000 bytes (333*3=999),建表成功
Query OK, 0 rows affected (0.07 sec) mysql> create table test3(id varchar(300),name varchar(34),key(id,name)) engine=myisam; >>多列索引,所有列长度大于1000 bytes 建表报错
ERROR 1071 (42000): Specified key was too long; max key length is 1000 bytes
mysql>
3. 问题解决方案
1) using col_name(length) syntax to specify an index prefix length.
对列的前面某部分创建索引
2) 启用innodb_large_prefix参数
- innodb_large_prefix >>启用innodb_large_prefix参数能够取消对于索引中每列长度的限制(但是无法取消对于索引总长度的限制)
- 启用innodb_large_prefix有如下前提条件:
- Enable this option to allow index key prefixes longer than 767 bytes (up to 3072 bytes) for InnoDB tables that use the DYNAMIC and COMPRESSED row formats.(Creating such tables also requires the option values innodb_file_format=barracuda and innodb_file_per_table=true.) >>启用innodb_large_prefix必须同时指定innodb_file_format=barracuda,innodb_file_per_table=true,并且建表的时候指定表的row_format为dynamic或者compressed(mysql 5.6中row_format默认值为compact)
- See Section 14.6.7, “Limits on InnoDB Tables” for the relevant maximums associated with index key prefixes under various settings. >>
- For tables using the REDUNDANT and COMPACT row formats, this option does not affect the allowed key prefix length.
innodb_large_prefix >>启用innodb_large_prefix参数能够取消对于索引中每列长度的限制(但是无法取消对于索引总长度的限制)
启用innodb_large_prefix有如下前提条件:
Enable this option to allow index key prefixes longer than 767 bytes (up to 3072 bytes) for InnoDB tables that use the DYNAMIC and COMPRESSED row formats.(Creating such tables also requires the option values innodb_file_format=barracuda and innodb_file_per_table=true.) >>启用innodb_large_prefix必须同时指定innodb_file_format=barracuda,innodb_file_per_table=true,并且建表的时候指定表的row_format为dynamic或者compressed(mysql 5.6中row_format默认值为compact)
See Section 14.6.7, “Limits on InnoDB Tables” for the relevant maximums associated with index key prefixes under various settings. >>
For tables using the REDUNDANT and COMPACT row formats, this option does not affect the allowed key prefix length.
例子如下:
- 1. 查看innodb_large_prefix,innodb_file_format参数
- mysql> show variables like 'innodb_large_prefix';
- +---------------------+-------+
- | Variable_name | Value |
- +---------------------+-------+
- | innodb_large_prefix | OFF |
- +---------------------+-------+
- 1 row in set (0.01 sec)
- mysql> show variables like 'innodb_file_format';
- +--------------------+----------+
- | Variable_name | Value |
- +--------------------+----------+
- | innodb_file_format | Antelope |
- +--------------------+----------+
- 1 row in set (0.00 sec)
- 2. 建索引测试(innodb_large_prefix,innodb_file_format都为默认值的情况下)
- mysql> create table test3(id varchar(256),key (id));
- ERROR 1709 (HY000): Index column size too large. The maximum column size is 767 bytes.
- mysql> create table test3(id varchar(255),name varchar(255),name1 varchar(255),name2 varchar(255),name3 varchar(5),key (id,name,name1,name2,name3));
- ERROR 1071 (42000): Specified key was too long; max key length is 3072 bytes
- ##索引列大于767 bytes时报错,组合索引列的总长度大于3072 bytes时报错
- 3. 修改innodb_large_prefix,innodb_file_format参数
- mysql> set global innodb_large_prefix=1;
- Query OK, 0 rows affected (0.00 sec)
- mysql> set global innodb_file_format=BARRACUDA;
- Query OK, 0 rows affected (0.00 sec)
- 4. 对row_format为dynamic格式表创建索引测试
- mysql> create table test3(id varchar(256),key (id)) row_format=dynamic;
- Query OK, 0 rows affected (0.14 sec)
- mysql> create table test3(id varchar(255),name varchar(255),name1 varchar(255),name2 varchar(255),name3 varchar(5),key (id,name,name1,name2,name3)) row_format=dynamic;
- ERROR 1071 (42000): Specified key was too long; max key length is 3072 bytes
- ##innodb_large_prefix=1并且innodb_file_format=BARRACUDA时,对于row_format为dynamic的表可以指定索引列长度大于767 bytes。但是索引列总长度的不能大于3072 bytes的限制仍然存在
1. 查看innodb_large_prefix,innodb_file_format参数
mysql> show variables like 'innodb_large_prefix';
+---------------------+-------+
| Variable_name | Value |
+---------------------+-------+
| innodb_large_prefix | OFF |
+---------------------+-------+
1 row in set (0.01 sec) mysql> show variables like 'innodb_file_format';
+--------------------+----------+
| Variable_name | Value |
+--------------------+----------+
| innodb_file_format | Antelope |
+--------------------+----------+
1 row in set (0.00 sec) 2. 建索引测试(innodb_large_prefix,innodb_file_format都为默认值的情况下)
mysql> create table test3(id varchar(256),key (id));
ERROR 1709 (HY000): Index column size too large. The maximum column size is 767 bytes. mysql> create table test3(id varchar(255),name varchar(255),name1 varchar(255),name2 varchar(255),name3 varchar(5),key (id,name,name1,name2,name3));
ERROR 1071 (42000): Specified key was too long; max key length is 3072 bytes
##索引列大于767 bytes时报错,组合索引列的总长度大于3072 bytes时报错 3. 修改innodb_large_prefix,innodb_file_format参数
mysql> set global innodb_large_prefix=1;
Query OK, 0 rows affected (0.00 sec)
mysql> set global innodb_file_format=BARRACUDA;
Query OK, 0 rows affected (0.00 sec) 4. 对row_format为dynamic格式表创建索引测试
mysql> create table test3(id varchar(256),key (id)) row_format=dynamic;
Query OK, 0 rows affected (0.14 sec) mysql> create table test3(id varchar(255),name varchar(255),name1 varchar(255),name2 varchar(255),name3 varchar(5),key (id,name,name1,name2,name3)) row_format=dynamic;
ERROR 1071 (42000): Specified key was too long; max key length is 3072 bytes
##innodb_large_prefix=1并且innodb_file_format=BARRACUDA时,对于row_format为dynamic的表可以指定索引列长度大于767 bytes。但是索引列总长度的不能大于3072 bytes的限制仍然存在
索引长度过长 ERROR 1071 (42000): Specified key was too long; max key length is 767 bytes的更多相关文章
- ERROR 1071 (42000): Specified key was too long; max key length is 767 bytes
今天在MySQL 5.6版本的数据库中修改InnoDB表字段长度时遇到了"ERROR 1071 (42000): Specified key was too long; max key le ...
- ERROR 1071 (42000): Specified key was too long; max key length is 1000 bytes
这个错误是我在安装ambari平台时,准备为ambari指定mysql数据库时,执行建表语句时遇到的. ERROR 1071 (42000): Specified key was too long; ...
- 【laravel5.6】 Illuminate\Database\QueryException : SQLSTATE[42000]: Syntax error or access violation: 1071 Specified key was too long; max key length is 1000 bytes
在进行数据迁移时候报错: 特殊字段太长报错, php artisan migrate 现在utf8mb4包括存储emojis支持.如果你运行MySQL v5.7.7或者更高版本,则不需要做任何事情. ...
- Using innodb_large_prefix to avoid ERROR #1071,Specified key was too long; max key length is 1000 bytes
Using innodb_large_prefix to avoid ERROR 1071 单列索引限制上面有提到单列索引限制767,起因是256×3-1.这个3是字符最大占用空间(ut ...
- laravel migrate时报错:Syntax error or access violation: 1071 Specified key was too long; max key length is 767 bytes
今天在学习laravel的路由模型绑定时,在按照文档执行php artisan migrate时报错. In Connection.php line 664: SQLSTATE[42000]: Syn ...
- laravel错误1071 Specified key was too long; max key length is 1000 bytes
Laravel 5.5 环境,php artisan migrate 之后,出现错误如题. 检查了一下,代码是这样的: $table->increments('id'); $table-> ...
- laravel 错误 1071 Specified key was too long; max key length is 1000 bytes
laravel 执行 php artisan migrate 安装数据库报 1071 Specified key was too long; max key length is 1000 bytes ...
- 导入sql文件报错:1071 Specified key was too long; max key length is 767 bytes
ref: https://stackoverflow.com/questions/1814532/1071-specified-key-was-too-long-max-key-length-is-7 ...
- django.db.utils.OperationalError: (1071, 'Specified key was too long; max key length is 767 bytes')
环境介绍 Django (2.1) Python 3.5.5 mysqlclient (1.4.2.post1) Mysql 5.6.28 RHEL 7.3 在migrate时候报错 model代码 ...
随机推荐
- ViewPage + RadioGroup + Fragment学习
底部是RadioGroup中RadioButton的切换.上面时ViewPage ,能够滑动,假设你们的需求是不须要滑动的话,那就直接用FrameLayout就能够了. 以下将会用两种方式实现.请大家 ...
- javascript---对象和函数的引用、浅拷贝、深拷贝、递归
1.javascript 对象和函数的引用 <!doctype html> <html lang="en"> <head> <meta c ...
- 如何设置mysql登陆密码?
此情况用于mysql密码为空. 命令如下: Mysqladmin –uroot password root1234 Root是用户名,root1234是新设置的密码
- 远程binlog
binlog介绍 binlog,即二进制日志,它记录了数据库上的所有改变. 改变数据库的SQL语句执行结束时,将在binlog的末尾写入一条记录,同时通知语句解析器,语句执行完毕. binlog格式 ...
- 使用 C# 开发智能手机软件:推箱子(十二)
这是"使用 C# 开发智能手机软件:推箱子"系列文章的第十二篇.在这篇文章中,介绍 Window/AboutDlg.cs 源程序文件. 这个源程序文件包括 AboutDlg 类,该 ...
- 重要:VC DLL编程
VC DLL编程 静态链接:每个应用程序使用函数库,必须拥有一份库的备份.多个应用程序运行时,内存中就有多份函数库代码的备份. 动态连接库:多个应用程序可以共享一份函数库的备份. DLL的调用方式:即 ...
- Linux内核源代码分析方法
Linux内核源代码分析方法 一.内核源代码之我见 Linux内核代码的庞大令不少人"望而生畏",也正由于如此,使得人们对Linux的了解仅处于泛泛的层次.假设想透析Linux ...
- 架构-LAMP特级学习(网站大访问量解决方案)
网站运营要面对的四个问题总结: 1.大访问量(主用负载均衡技术) 2.大存储量 3.访问速度 4.服务器监控 一.大访问量解决方案 超级计算机 = 负载均衡 + 集群 0.反向代理(Nginx等实现) ...
- '<>' operator is not allowed for source level below 1.7
报错:'<>' operator is not allowed for source level below 1.7 这是eclipse的编译环境与项目的要求不对应造成的,这个错误一般是导 ...
- JNI入门
JNI是Java Native Interface的缩写,Native指C/C++. JNI内容涉及两个方面: Java调用C,这种情况是最主要的 C调用Java,这种情况不常见 第一步:编写Java ...