在MySQL5.7及以后版本中,在创建表、更改表等操作时,报ERROR 1118 (42000): Row size too large (> 8126). Changing some columns to TEXT or BLOB may help. In current row format, BLOB prefix of 0 bytes is stored inline.错误。如下所示: mysql> SHOW VARIABLES LIKE 'innodb_strict_mode'; +--------------------+-------+ | Variable_name | Value | +--------------------+-------+ | innodb_strict_mode | ON | +--------------------+-------+ 1 row in set (0.01 sec) mysql> CREATE TABLE 'my_data' ( -> 'id' int(11) NOT NULL AUTO_INCREMENT, -> 'mid' int(11) NOT NULL DEFAULT '1', -> 'oid' bigint(20) NOT NULL, ... -> 'txt' varchar(4) DEFAULT '-1', -> PRIMARY KEY ('id'), -> UNIQUE KEY 'count' ('app_count'), -> UNIQUE KEY 'Email' ('txtEmail'), -> KEY 'uid' ('uid') USING BTREE, -> KEY 'idx_start_date' ('start_date') -> ) ENGINE=InnoDB AUTO_INCREMENT=5258 DEFAULT CHARSET=utf8 ROW_FORMAT=DYNAMIC; ERROR 1118 (42000): Row size too large (> 8126). Changing some columns to TEXT or BLOB may help. In current row format, BLOB prefix of 0 bytes is stored inline. mysql> SHOW TABLES; Empty set (0.00 sec)可以通过临时设置innodb_strict_mode为OFF,然后使报错信息以警告的方式提示,而不是直接以ERROR的方式中断表的创建,如下所示。 mysql> SET SESSION innodb_strict_mode = OFF; Query OK, 0 rows affected (0.00 sec) ERROR 1064 (42000): You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'VARA' at line 1 mysql> SHOW VARIABLES LIKE 'innodb_strict_mode'; +--------------------+-------+ | Variable_name | Value | +--------------------+-------+ | innodb_strict_mode | OFF | +--------------------+-------+ 1 row in set (0.01 sec) mysql> mysql> CREATE TABLE 'my_data' ( -> 'id' int(11) NOT NULL AUTO_INCREMENT, -> 'mid' int(11) NOT NULL DEFAULT '1', -> 'oid' bigint(20) NOT NULL, ... -> 'txt' varchar(4) DEFAULT '-1', -> PRIMARY KEY ('id'), -> UNIQUE KEY 'count' ('app_count'), -> UNIQUE KEY 'Email' ('txtEmail'), -> KEY 'uid' ('uid') USING BTREE, -> KEY 'idx_start_date' ('start_date') -> ) ENGINE=InnoDB AUTO_INCREMENT=5258 DEFAULT CHARSET=utf8 ROW_FORMAT=DYNAMIC -> -> ; Query OK, 0 rows affected, 1 warning (0.12 sec) mysql> SHOW WARNINGS; +---------+------+----------------------------------------------------------------------------------------------------------------------------------------------+ | Level | Code | Message | +---------+------+----------------------------------------------------------------------------------------------------------------------------------------------+ | Warning | 139 | Row size too large (> 8126). Changing some columns to TEXT or BLOB may help. In current row format, BLOB prefix of 0 bytes is stored inline. | +---------+------+----------------------------------------------------------------------------------------------------------------------------------------------+ 1 row in set (0.00 sec) mysql> SHOW TABLES; +--------------------+ | Tables_in_test | +--------------------+ | my_data | +--------------------+ 1 row in set (0.00 sec) mysql>也可以通过更改表的存储引擎和存储方式来临时解决,最好还是调整表的设计,满足数据库要求的限制条件。
Row size too large (> 8126)解决办法
来源:这里教程网
时间:2026-03-01 15:23:05
作者:
编辑推荐:
- Row size too large (> 8126)解决办法03-01
- MySQL 5.6使用pt-online-schema-change在线修改大表字段长度03-01
- 从全备中恢复单库或单表,小心有坑!03-01
- 怎样让企业数据加密03-01
- MySQL:用户03-01
- MyCAT之读写分离03-01
- 关于MySQL参数,这些你要知道03-01
- 使用通用二进制文件在Linux系统上安装MySQL03-01
下一篇:
相关推荐
-
雷神推出 MIX PRO II 迷你主机:基于 Ultra 200H,玻璃上盖 + ARGB 灯效
2 月 9 日消息,雷神 (THUNDEROBOT) 现已宣布推出基于英
-
制造商 Musnap 推出彩色墨水屏电纸书 Ocean C:支持手写笔、第三方安卓应用
2 月 10 日消息,制造商 Musnap 现已在海外推出一款 Oce
热文推荐
- MyCAT之读写分离
MyCAT之读写分离
26-03-01 - 使用通用二进制文件在Linux系统上安装MySQL
使用通用二进制文件在Linux系统上安装MySQL
26-03-01 - MySQL latch争用深入分析
MySQL latch争用深入分析
26-03-01 - MySQL InnoDB脏页管理
MySQL InnoDB脏页管理
26-03-01 - MySQL checkpoint
MySQL checkpoint
26-03-01 - 淘太尉是如何实现淘宝首页添加一键直达微博链接的
淘太尉是如何实现淘宝首页添加一键直达微博链接的
26-03-01 - 这些著名数据库之间的“关系”,你知道吗?
这些著名数据库之间的“关系”,你知道吗?
26-03-01 - MySQL基准测试多线程复制的效率
MySQL基准测试多线程复制的效率
26-03-01 - MySQL死锁案例二(自增列导致死锁)
MySQL死锁案例二(自增列导致死锁)
26-03-01 - MySQL死锁案例一(回滚导致死锁)
MySQL死锁案例一(回滚导致死锁)
26-03-01
