I’m having the same error on my end. Did you find a resolution for the error:
“Database error 1406 while doing query Data too long for column ‘data’ at row 1”?
funny… i came across this error again today on an install. i ended up at this page, but saw that it was still the original question and mine. i went to close the tab and then saw your reply! …so random.
i cannot recall how i fixed it last time, but i ‘feel’ that it might have had something to do with the table not being utf8_general_ci… and taking it apart and putting it back together. it was too many years back for me to remember though
There are quite a fee of those questions arround here
Thanks for the feedback. The process actually seems to follow on, so no major issue. I just dislike touching database definitions thinking of future updates issues.
If this is indeed the cause and solution, the way forward is to go to your Cpanel (NOT phpList admin pages) and access the phpMyAdmin, locate the database your phpList is using, Export all database tables, for safety.
Next, in the left hand side of the screen, select the database you wish to work on.
Then, on the right hand side of the screen, select Operations tab.
Now, find the Collation section. Using the dropdown menu under Collation, find utf8_general_ci, select this. Now click Go.
This will change your database from a mixture of formats (mine included 6 x latin1_swedish_ci) to uti8_general_ci
thanks @luison, but i actually can’t take credit for it. i stumbled upon that (or saw a clue implying that) elsewhere. …just can’t remember where or when. hah
so… sorry to be a downer, but i’m not sure if that ended up working for me. i have a super old base install, so i’m not sure if that’s the root of my issue.
i dumped out (mysqldump) the old DB and imported it back in (it’s 1.2gb )
i converted blob to blobmedium (which appeared to initially work for me)
…but am still seeing that error line pop up. sometimes, it’s even showing twice.
– “Database error 1406 while doing query Data too long for column ‘data’ at row 1”
is there any specific reason why blob is being used? i don’t know enough about MySQL to know that answer, but i can’t help but wonder if the issue would go away if the table was converted.
i figured, “well hey… why not simply remove row 1 from the spreadsheet?” …but, I believe that might be what caused the line to show twice.
i’m also randomly seeing “the mysql database has gone away”, which is kind of new. i have a feeling that might be attributed to CloudLinux’s CageFS system. it was set to kill off slow queries that took longer than 30 seconds to execute. i added an exception for the account and also raised the timeout to 60, but i haven’t seen the results of everything yet.
i cleaned up some of my tables, as they were nearly 2gb in size, and that appears to have fixed things up a little bit. everything is running faster now (bounce processing wise), but the error is still showing up.
randomly enough… i received this error, just after i submitted my last reply:
Database error 2006 while doing query MySQL server has gone away
Database error 2006 while doing query MySQL server has gone away
Database error 2006 while doing query MySQL server has gone away
Database error 2006 while doing query MySQL server has gone away
Database error 2006 while doing query MySQL server has gone away
Database error 2006 while doing query MySQL server has gone away
.... and on and on and on and on
i looked into the MySQL error log and saw this error line:
host: 'localhost' (Got a packet bigger than 'max_allowed_packet' bytes)
it was set to 32M. I’m going to change:
[mysql]
max_allowed_packet = 32M
[mysqld]
max_allowed_packet = 64M
After switching from PHP 7.0.x to PHP 7.1.x I am now seeing many of these errors when I process bounces:
Database error 1406 while doing query Data too long for column ‘data’ at row 1
and this one time error:
Database error 1366 while doing query Incorrect string value: ‘\xE9 ause…’ for column ‘header’ at row 1
My tables are all utf8_general_ci, however, for some reason, the database itself is latin1_swedish_ci. I am not sure if this could cause the issues, but would appreciate any input here. My max_allowed_packet = 256M so I doubt that is the issue.