ERROR 1074 (42000): Column length too big for column 'Flist' (max = 21845); use BLOB or TEXT instead

1.版本

1)操作系统

cat /etc/issue

cat /etc/issue

CentOS release 6.6 (Final)

Kernel \r on an \m

cat /proc/version

cat /proc/version

Linux version 2.6.32-504.el6.x86_64 ([email protected]) (gcc version 4.4.7 20120313 (Red Hat 4.4.7-11) (GCC) ) #1 SMP Wed Oct 15 04:27:16 UTC 2014

2)mysql数据库版本

MySQL --version

mysql  Ver 14.14 Distrib 5.6.26, for linux-glibc2.5 (x86_64) using  EditLine wrapper

2. 问题描述

建表语句报如下错误:

CREATE TABLE test_1 (
							Fid bigint(20) unsigned NOT NULL,
							Ftype tinyint(4) unsigned NOT NULL,
							Flist varchar(65532) DEFAULT NULL,
							Fstatus tinyint(3) unsigned DEFAULT '0',
							Ftime bigint unsigned DEFAULT '0',
							Faddtime bigint unsigned DEFAULT '0',
							PRIMARY KEY (Fid,Ftype)
						) ENGINE=InnoDB DEFAULT CHARSET=utf8;
建表报如下错误:
ERROR 1074 (42000): Column length too big for column 'Flist' (max = 21845); use BLOB or TEXT instead

3. 问题分析

3.1 原因分析

虽然知道mysql建表的时候列长度有65535的限制,但是一直没有时间整理这个问题,接着今天整理一下。

ERROR 1074 (42000): Column length too big for column ‘Flist‘ (max = 21845); use BLOB or TEXT instead

从上面的报错我们知道Flist列指定值不能大于21845 字节(mysql官方手册中定义,创建表的字段长度限制为65535 bytes,这个是指所有列指定的长度和,当然不包括TEXT和BLOB类型的字段)。

还有一点我们需要注意的是我们定义列长度时指定的长度单位为字符,上面提到的65535限制的单位为字节。不同字符集下每个字符占用的字节数不同,utf8下每个字符占用3个字节(65535/3=21845),gbk下每个字符占用2个字节(65535/2=32767),latin1字符集下一个字符占用一个字节。

3.2  操作验证

<span style="color:#333333;">实验1:
CREATE TABLE test_1 (
							Flist varchar(21845) DEFAULT NULL
						) ENGINE=InnoDB DEFAULT CHARSET=utf8;
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
</span><span style="color:#ff0000;">##我们发现给表指定一个列,列长度为21845字符(utf8下最大长度限制),但是建表依然报错。这是因为还有别的一些开销,所以我们不能指定列长度为最大限制21845(测试发现指定长度为21844后建表成功)</span>
<span style="color:#333333;">实验2:
CREATE TABLE test_1 (
							Fid bigint(20) unsigned NOT NULL,
							Ftype tinyint(4) unsigned NOT NULL,
							Flist varchar(21844) DEFAULT NULL,
							Fstatus tinyint(3) unsigned DEFAULT '0',
							Ftime bigint unsigned DEFAULT '0',
							Faddtime bigint unsigned DEFAULT '0',
							PRIMARY KEY (Fid,Ftype)
						) ENGINE=InnoDB DEFAULT CHARSET=utf8;
报如下错误:
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
</span><span style="color:#ff0000;">##虽然Flist 长度指定为21844,但是因为还有其他非TEXT和BLOB字段存在,所以报错。这是因为65535长度限制是针对表中所有列的长度和的最大限制,如果列的长度和超过该值,建表依然会报错。(除了TEXT和BLOB类型的字段的)</span>

##注意从实验2中我们可以看出来65535并非只是针对varchar类型的长度限制(这个和姜承尧大师innodb存储引擎第二版中相关描述有些出入)

4. 解决方案

1. 使用TEXT或者BLOB类型替换varchar类型

2. 缩小varchar类型指定的字符长度

ERROR 1074 (42000): Column length too big for column 'Flist' (max = 21845); use BLOB or TEXT instead

时间: 2024-08-02 11:21:08

ERROR 1074 (42000): Column length too big for column 'Flist' (max = 21845); use BLOB or TEXT instead的相关文章

1074, &quot;Column length too big for column &#39;err_solution&#39; (max = 21845); use BLOB or TEXT instead&quot;

一个注意点,就是sqlalchemy 使用create_all()建表的时候,要在 create_all()所在页面import那些表的model sqlalchemy.exc.OperationalError: (_mysql_exceptions.OperationalError) (1074, "Column length too big for column 'err_solution' (max = 21845); use BLOB or TEXT instead") [SQ

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 length is 767 bytes"错误,第一次遇到这个错误,遂花了点学习.研究过.总结这个问题. 我们先来创建一个测试表,构造这样的错误. mysql> use MyDB; Reading table information for completion of table and colum

php artisan migrate时出现 SQLSTATE[42000]: Syntax error or access violation: 1071 Specified key was too long; max key length is 1000 bytes解决办法

在测试队列中运用artisan命令行 php artisan queue:table php artisan migrate时出现 SQLSTATE[42000]: Syntax error or access violation: 1071 Specified key was too long; max key length is 1000 bytes Change database.php which is in config folder where it says 'charset' =

mysql异常ERROR 1055 (42000)说明

具体异常信息如下: ERROR 1055 (42000): Expression #1 of SELECT list is not in GROUP BY clause and contains nonaggregated column 'aaa.test.age' which is not functionally dependent on columns in GROUP BY clause;  this is incompatible with sql_mode=only_full_gro

MySQL Error--InnoDB Table mysqlinnodb_index_stats has length mismatch in the column

使用MySQL 5.7.24版本的安装文件替换MySQL 5.7.19版本的安装文件,数据库复制频繁中断,查看error日志发现下面错误: [Warning] InnoDB: Table mysql/innodb_index_stats has length mismatch in the column name table_name. Please run mysql_upgrade 解决办法: 在MySQL服务正常运行的状态下,使用mysql_upgrade命令进行处理: mysql_upg

laravel migrate时报错:Syntax error or access violation: 1071 Specified key was too long; max key length is 767 bytes

在按照文档执行php artisan migrate时报错. SQLSTATE[42000]: Syntax error or access violation: 1071 Specified key was too long; max key length is 767 bytes (SQL: alter table `users` add unique `users_email_unique`(`email`)) 解决方法 namespace App\Providers; use Illum

Laravel 5.4 migrate报错:Syntax error or access violation: 1071 Specified key was too long; max key length is 767 bytes (SQL: alter table `users` add unique `us ers_email_unique`(`email`))

Laravel 5.4 migrate报错:Syntax error or access violation: 1071 Specified key was too long; max key length is 767 bytes (SQL: alter table `users` add unique `us     ers_email_unique`(`email`)) public function up() { Schema::create('users', function (Blu

删除或清空具有外键约束的表数据报-ERROR 1701 (42000)

OS:  centos 6.3 DB:5.5.14 mysql> select database();+------------+| database() |+------------+| sakila     |+------------+1 row in set (0.00 sec) mysql> delete from actor;ERROR 1451 (23000): Cannot delete or update a parent row: a foreign key constra

RDS还原数据库时报错:ERROR 1227 (42000) at line 78664

最近公司准备公司的整套架构从IDC机房向云上迁移,在RDS上做数据库恢复的时候遇到如下的问题: [[email protected] ~]# mysql -uadmin -h 10.137.212.36 -p </root/mysql_dump.sql Enter password: ERROR 1227 (42000) at line 78664: Access denied; you need (at least one of) the SUPER privilege(s) for this