[MySQL 错误]ERROR 1118 (42000): Row size too large. The maximum row size for the used table type, not...-优快云博客

本文记录了一次在MySQL中创建表时遇到的错误，并详细解释了如何通过调整字段类型从varchar到text来解决因行尺寸过大导致的问题。

摘要生成于 C知道，由 DeepSeek-R1 满血版支持，前往体验 >

朋友发过来一个SQL,，让我执行以下：

CREATE TABLE `ttt` (
	`id` DOUBLE ,
	`select_type` VARCHAR (57),
	`table` VARCHAR (192),
	`type` VARCHAR (30),
	`possible_keys` VARCHAR (22288),
	`key` VARCHAR (192),
	`key_len` VARCHAR (22288),
	`ref` VARCHAR (3072),
	`rows` DOUBLE ,
	`Extra` VARCHAR (765)
); 
INSERT INTO `ttt` (`id`, `select_type`, `table`, `type`, `possible_keys`, `key`, `key_len`, `ref`, `rows`, `Extra`) VALUES('1','PRIMARY','aaa','index',NULL,'email_2','51',NULL,'5','Using where; Using index');
INSERT INTO `ttt` (`id`, `select_type`, `table`, `type`, `possible_keys`, `key`, `key_len`, `ref`, `rows`, `Extra`) VALUES('2','DEPENDENT SUBQUERY','bbb','ref','id','id','5','test.aaa.id','1','Using where; Using index');

执行第一句建表的时候就卡住了，报错如下：

mysql> CREATE TABLE `ttt` (
    -> `id` DOUBLE ,
    -> `select_type` VARCHAR (57),
    -> `table` VARCHAR (192),
    -> `type` VARCHAR (30),
    -> `possible_keys` VARCHAR (12288),
    -> `key` VARCHAR (192),
    -> `key_len` VARCHAR (12288),
    -> `ref` VARCHAR (3072),
    -> `rows` DOUBLE ,
    -> `Extra` VARCHAR (765)
    -> ); 
ERROR 1118 (42000): Row size too large. The maximum row size for the used table type, not counting BLOBs, is 65535. This includes storage overhead, check the manual. You have to change some columns to TEXT or BLOBs
mysql>

看了提示，表的2个varchar字段长度设置过长了，需要改成text，blob之类的类型，修改之后执行成功了：

mysql> use test;
Database changed
mysql> 
mysql> CREATE TABLE `ttt` (
    -> `id` DOUBLE ,
    -> `select_type` VARCHAR (57),
    -> `table` VARCHAR (192),
    -> `type` VARCHAR (30),
    -> `possible_keys` TEXT,
    -> `key` VARCHAR (192),
    -> `key_len`  TEXT,
    -> `ref` VARCHAR (3072),
    -> `rows` DOUBLE ,
    -> `Extra` VARCHAR (765)
    -> ); 
Query OK, 0 rows affected (0.00 sec)

mysql> INSERT INTO `ttt` (`id`, `select_type`, `table`, `type`, `possible_keys`, `key`, `key_len`, `ref`, `rows`, `Extra`) VALUES('1','PRIMARY','aaa','index',NULL,'email_2','51',NULL,'5','Using where; Using index');
Query OK, 1 row affected (0.04 sec)

mysql> INSERT INTO `ttt` (`id`, `select_type`, `table`, `type`, `possible_keys`, `key`, `key_len`, `ref`, `rows`, `Extra`) VALUES('2','DEPENDENT SUBQUERY','bbb','ref','id','id','5','test.aaa.id','1','Using where; Using index');
Query OK, 1 row affected (0.00 sec)

mysql> select * from ttt;
+------+--------------------+-------+-------+---------------+---------+---------+-------------+------+--------------------------+
| id   | select_type        | table | type  | possible_keys | key     | key_len | ref         | rows | Extra                    |
+------+--------------------+-------+-------+---------------+---------+---------+-------------+------+--------------------------+
|    1 | PRIMARY            | aaa   | index | NULL          | email_2 | 51      | NULL        |    5 | Using where; Using index |
|    2 | DEPENDENT SUBQUERY | bbb   | ref   | id            | id      | 5       | test.aaa.id |    1 | Using where; Using index |
+------+--------------------+-------+-------+---------------+---------+---------+-------------+------+--------------------------+
2 rows in set (0.00 sec)

疑惑：varchar(N)，这个N不是最大为65535吗？为什么设置成12288就会报错？12288比65535小很多啊。

有问题上官网：http://dev.mysql.com/doc/refman/5.6/en/char.html

In contrast toCHAR,VARCHARvalues are stored as a 1-byte or 2-byte length prefix plus data. The length prefix indicates the number of bytes in the value. A column uses one length byte if values require no more than 255 bytes, two length bytes if values may require more than 255 bytes.

原来有N有255这样一个坎啊，超过了N的意义就不一样了。