ExpressionEngine 7.5 has been Released! Learn More!
Hi All! “An error occurred while importing SQL”
I’m sure I’ve seen things like this discussed before … hopefully there is a quick fix or something
I’m trying to load a db backup taken from a site running EE7.3.15. Site is running MariaDB 10.4.28. The site I’m trying to load it to is also running MariaDB 10.4.28.
The db is quite large (1.21GB).
The import fails when trying to load exp_channel_data - the failure comes with the error message:
[ERROR in query 296] 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.
Does anyone have any thoughts about what I can do to persuade the local db to load the SQL? Or perhaps some ideas about some other way of loading the database other than export->sql->import Thanks in advance for any thoughts / guidance / ideas!
This happens to me, especially with pulling in old databases. Tom has the following suggestion, which has always worked for me.
So you can break fields out of their old way of storage and into the new one to avoid this. You should be able to do the import with the following added to your mysql conf.
[mysqld] innodb_file_per_table=1 innodb_file_format=Barracuda innodb_file_format_check = ON innodb_log_file_size = 1G innodb_strict_mode = 0
Or you can disable strict mode via mysql command:
SET SESSION innodb_strict_mode=OFF;
Packet Tide owns and develops ExpressionEngine. © Packet Tide, All Rights Reserved.