Mysql Error 1118

here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more mysql row size too large 65535 about Stack Overflow the company Business Learn more about hiring developers or posting

Syntax Error Or Access Violation 1118 Row Size Too Large 8126

ads with us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack mysql increase row size Overflow is a community of 6.2 million programmers, just like you, helping each other. Join them; it only takes a minute: Sign up MySQL Error 1118 (Row size too large) when restoring Django-mailer database change innodb_log_file_size up vote 7 down vote favorite 2 I dumped a working production database from a django app and am trying to migrate it to my local development environment. The production server runs MySQL 5.1, and locally I have 5.6. When migrating the django-mailer's "messagelog" table, I'm running into the dreaded Error 1118: ERROR 1118 (42000) at line 2226: Row size too large (> 8126). Changing some columns to TEXT

Innodb_strict_mode = 0

or BLOB may help. In current row format, BLOB prefix of 0 bytes is stored inline. I've read lots of stuff online about this error, but none of it has solved my problem. N.B. This error is not coming from the creation of the table, but rather the insertion of a row with pretty large data. Notes: The innodb_file_format and innodb_file_format_max variables are set to Barracuda. The ROW_FORMAT is set to DYNAMIC on table creation. The table does not have very many columns. Schema below: +----------------+------------+------+-----+---------+----------------+ | Field | Type | Null | Key | Default | Extra | +----------------+------------+------+-----+---------+----------------+ | id | int(11) | NO | PRI | NULL | auto_increment | | message_data | longtext | NO | | NULL | | | when_added | datetime | NO | | NULL | | | priority | varchar(1) | NO | | NULL | | | when_attempted | datetime | NO | | NULL | | | result | varchar(1) | NO | | NULL | | | log_message | longtext | NO | | NULL | | +----------------+------------+------+-----+---------+----------------+ Again, the error happens ONLY when I try to insert a quite large (message_data is about 5 megabytes) row; creating the table works fine

here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About innodb_log_file_size mysql Us Learn more about Stack Overflow the company Business Learn more about hiring developers innodb_file_format=barracuda or posting ads with us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack

Row_format=dynamic

Overflow Community Stack Overflow is a community of 6.2 million programmers, just like you, helping each other. Join them; it only takes a minute: Sign up ERROR 1118 (42000) Row size too large http://stackoverflow.com/questions/25299370/mysql-error-1118-row-size-too-large-when-restoring-django-mailer-database up vote 6 down vote favorite 2 I know that this question has been asked (and answered) many times, but none of them appear to be the same problem that I am seeing... The table that is giving me problems only has two columns: the first field is an integer, the second field is longtext. Here is a portion of a dump file from MySQL 5.5.30: http://stackoverflow.com/questions/25163614/error-1118-42000-row-size-too-large 1 - MySQL dump 10.13 Distrib 5.5.30, for Linux (x86_64) 2 -- 3 -- Host: localhost Database: mydatabasename 4 -- ------------------------------------------------------ 5 -- Server version 5.5.30-log 32 DROP TABLE IF EXISTS `large_file`; 33 /*!40101 SET @saved_cs_client = @@character_set_client */; 34 /*!40101 SET character_set_client = utf8 */; 35 CREATE TABLE `large_file` ( 36 `id` int(11) NOT NULL AUTO_INCREMENT, 37 `data` longtext, 38 PRIMARY KEY (`id`) 39 ) ENGINE=InnoDB AUTO_INCREMENT=59 DEFAULT CHARSET=latin1; 40 /*!40101 SET character_set_client = @saved_cs_client */; 43 -- Dumping data for table `large_file` 44 -- 45 46 LOCK TABLES `large_file` WRITE; 47 /*!40000 ALTER TABLE `large_file` DISABLE KEYS */; 48 INSERT INTO `large_file` VALUES(38,'GyUtMTIzNDVYQ... ...); 49 /*!40000 ALTER TABLE `large_file` ENABLE KEYS */; 50 UNLOCK TABLES; As you can see this dump file came from MySQL 5.5.30, and I can import this data into 5.5.30. But, when I try to import into 5.6.x, I get the ERROR 1118 (42000) Row size too large error. The data going into the large_file table, is (relatively) large, values range in size from 15 MB to about 25 MB. The data is all ASCII (base 64 encoded). Other posters have had issues with very large number of columns,

here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company http://stackoverflow.com/questions/29401909/mysql-error-code-1118-row-size-too-large-8126 Business Learn more about hiring developers or posting ads with us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 6.2 million programmers, just like you, helping each other. Join them; it only takes a minute: Sign up MySQL “Error Code: 1118. Row size too large (> 8126)” up vote 0 down vote favorite I have two installs of MySQL. row size One is on my local Linux laptop and the other is on our Development Linux server. Both installs are the same version (mysql Ver 14.14 Distrib 5.6.23). When I run a create statement for a table on my local install it completes successfully. When I try to run that same create on the server it fails with the following error: Error Code: 1118. Row size too large (> 8126). Changing some columns to TEXT row size too or BLOB or using ROW_FORMAT=DYNAMIC or ROW_FORMAT=COMPRESSED may help. In current row format, BLOB prefix of 768 bytes is stored inline. Obviously the two installs have different my.cnf configurations and hardware specs to back them. Are there any my.cnf specific settings that affect the row size limit or how it is calculated? I tried altering the "innodb-log-file-size" setting but it didn't have any affect on the error. I would rather not chunk my table into multiple tables if at all possible. mysql linux size row limit share|improve this question asked Apr 1 '15 at 22:22 Cymon 741411 Well there are reported bugs about this for InnoDB tables where it does include the text and blob column in the calculation even though it should not. Check for your specifc version at bugs.mysql.com –David Soussan Apr 1 '15 at 23:16 Possible duplicate of Change limit for "Mysql Row size too large" –pathikrit Dec 4 '15 at 0:05 add a comment| 1 Answer 1 active oldest votes up vote 0 down vote accepted The most common cause of this issue being different between servers is character set or innodb_log_file_size. See previous answers here: Change limit for "Mysql Row size too large" share|improve this answer answered Apr 1 '15 at 23:56 Trent Lloyd 1,2301710 add a comment| Your Answer