Go Premium for a chance to win a PS4. Enter to Win

x
?
Solved

MySQL Error message: SQLSTATE[42000]: Syntax error or access violation: 1118 Row size too large (> 8126)

Posted on 2015-01-05
6
Medium Priority
?
1,080 Views
Last Modified: 2016-06-17
Hi,

I have never seen this error message before - and am struggling to find a solution!

CDbCommand failed to execute the SQL statement: SQLSTATE[42000]: Syntax error or access violation: 1118 Row size too large (> 8126).

The offending row in the table was varchar 500, so the first thing I did was change that to LONGTEXT in the vain hope this would help - but to no avail.

The error message goes on to say "Changing some columns to TEXT 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."

There is unsual (at all) about the text being entered for this row and I've got other columns which are LONGTEXT with no problem at all !

Any help much appreciated !!!
0
Comment
Question by:daisydoos
  • 2
  • 2
5 Comments
 
LVL 84

Expert Comment

by:Dave Baldwin
ID: 40531073
How are you doing the insert?  What programming language?  And what version of MySQL are you using?
0
 
LVL 143

Expert Comment

by:Guy Hengel [angelIII / a3]
ID: 40531075
can you please show the full table description.
also, do you maybe have some trigger on the table that does something else behind?
0
 

Author Comment

by:daisydoos
ID: 40531178
Hi,

Many thanks for getting back to me. I'm using PHP. MySQL version is  5.5.35

Doesn't make any diffrence if I enter the data via the site admin or directly using PhpMyAdmin - get the same error emssage.

I've included the full table schema below - the offending columns are eg homeRightCol4 which as you can see I've now set to LONGTEXT (it was originally VARCHAR 500) ...

I have never come across this error before!!

Many thanks in advance!

CREATE TABLE IF NOT EXISTS `site_page` (
  `id` int(11) NOT NULL AUTO_INCREMENT,
  `moduleNameForSearch` char(4) NOT NULL DEFAULT 'page',
  `itemOrCatForSearch` varchar(4) NOT NULL DEFAULT 'cat',
  `name` varchar(255) NOT NULL,
  `indexID` varchar(255) NOT NULL,
  `type` int(3) NOT NULL DEFAULT '1',
  `meta_title` varchar(255) DEFAULT NULL,
  `meta_description` mediumtext,
  `meta_keywords` tinytext,
  `longdesc` longtext,
  `shortdesc` mediumtext,
  `homePageOnly` mediumtext NOT NULL,
  `homeVideo` mediumtext NOT NULL,
  `homeTopR1` mediumtext NOT NULL,
  `homeTopR2` mediumtext NOT NULL,
  `homeTopR3` mediumtext NOT NULL,
  `homeLeftCol1` mediumtext NOT NULL,
  `homeLeftCol2` mediumtext NOT NULL,
  `homeLeftCol3` mediumtext NOT NULL,
  `homeMidCol1` mediumtext NOT NULL,
  `homeMidCol2` mediumtext NOT NULL,
  `homeMidCol3` mediumtext NOT NULL,
  `homeMidCol4` mediumtext NOT NULL,
  `homeRightCol1` mediumtext NOT NULL,
  `homeRightCol2` mediumtext NOT NULL,
  `homeRightCol3` mediumtext NOT NULL,
  `homeRightCol4` longtext NOT NULL,
  `youTubeCode` mediumtext NOT NULL,
  `video_title` varchar(255) NOT NULL,
  `video_thumbnail_loc` varchar(400) NOT NULL,
  `video_file` varchar(400) NOT NULL,
  `video_duration` int(9) NOT NULL,
  `video_description` varchar(700) NOT NULL,
  `parent` int(3) NOT NULL,
  `level` int(2) NOT NULL DEFAULT '0',
  `public` int(1) NOT NULL DEFAULT '1',
  `inMainMenu` int(1) NOT NULL DEFAULT '1',
  `inSubMenu` int(1) NOT NULL DEFAULT '1',
  `inFooter` int(1) NOT NULL DEFAULT '0',
  `sort` int(11) NOT NULL DEFAULT '0',
  `visible` int(1) NOT NULL DEFAULT '1',
  `inSearchResults` int(1) NOT NULL DEFAULT '1',
  `inSiteMap` int(1) NOT NULL DEFAULT '1',
  `securePage` int(1) NOT NULL DEFAULT '1',
  `module` int(3) NOT NULL DEFAULT '1',
  `lang_id` int(3) NOT NULL DEFAULT '1',
  `site_id` int(3) NOT NULL DEFAULT '1',
  `multiLingual` int(1) NOT NULL DEFAULT '1',
  `multiSite` int(1) NOT NULL DEFAULT '0',
  `externalUrl` varchar(255) DEFAULT NULL,
  `created` datetime NOT NULL,
  `updated` datetime NOT NULL,
  `create_user_id` int(3) NOT NULL,
  `update_user_id` int(3) NOT NULL,
  PRIMARY KEY (`id`),
  KEY `type` (`type`),
  KEY `module` (`module`),
  KEY `lang_id` (`lang_id`),
  KEY `site_id` (`site_id`)
) ENGINE=InnoDB  DEFAULT CHARSET=latin1 AUTO_INCREMENT=60 ;
0
 
LVL 143

Accepted Solution

by:
Guy Hengel [angelIII / a3] earned 2000 total points
ID: 40531224
the "error" is not in the table definition "per se", but in the total data volume per row.

to "fix" this, you will need to split the table into several tables.

my suggestion would be to move:
`homePageOnly` mediumtext NOT NULL,
  `homeVideo` mediumtext NOT NULL,
  `homeTopR1` mediumtext NOT NULL,
  `homeTopR2` mediumtext NOT NULL,
  `homeTopR3` mediumtext NOT NULL,
  `homeLeftCol1` mediumtext NOT NULL,
  `homeLeftCol2` mediumtext NOT NULL,
  `homeLeftCol3` mediumtext NOT NULL,
  `homeMidCol1` mediumtext NOT NULL,
  `homeMidCol2` mediumtext NOT NULL,
  `homeMidCol3` mediumtext NOT NULL,
  `homeMidCol4` mediumtext NOT NULL,
  `homeRightCol1` mediumtext NOT NULL,
  `homeRightCol2` mediumtext NOT NULL,
  `homeRightCol3` mediumtext NOT NULL,
  `homeRightCol4` longtext NOT NULL,

into 1 table that "translates all those columns into rows" with:
`site_page_id' (foreign key)
section_key varchar(50) not null
section_data longtext

and do like this;
id  , 'homePageOnly',  ...
id  , 'homeVideo',  ...
etc ....

this technique will then not only avoid the error, but also make it much simpler to add new "columns" to your code: just adding a new row without having to change the "schema"
0
 

Author Comment

by:daisydoos
ID: 40531284
Hi,

Many thanks for getting back with this solution - that would make sense as the problem only occurred after adding a bunch of new rows. I was not aware of this restriction!
0

Featured Post

Get your Disaster Recovery as a Service basics

Disaster Recovery as a Service is one go-to solution that revolutionizes DR planning. Implementing DRaaS could be an efficient process, easily accessible to non-DR experts. Learn about monitoring, testing, executing failovers and failbacks to ensure a "healthy" DR environment.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

This post contains step-by-step instructions for setting up alerting in Percona Monitoring and Management (PMM) using Grafana.
In this series, we will discuss common questions received as a database Solutions Engineer at Percona. In this role, we speak with a wide array of MySQL and MongoDB users responsible for both extremely large and complex environments to smaller singl…
In this video, Percona Solution Engineer Dimitri Vanoverbeke discusses why you want to use at least three nodes in a database cluster. To discuss how Percona Consulting can help with your design and architecture needs for your database and infras…
In this video, Percona Solutions Engineer Barrett Chambers discusses some of the basic syntax differences between MySQL and MongoDB. To learn more check out our webinar on MongoDB administration for MySQL DBA: https://www.percona.com/resources/we…
Suggested Courses
Course of the Month5 days, 20 hours left to enroll

772 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question