Thread

My client wants to switch hosting, and the host is running MySQL 4.0.27-log, whereas their current hosting is running MySQL 5.0.24a-standard-log. I’ve tried an export to a .sql file of the EE database, and even massaged it to resolve domain name changes, server paths, etc. in the data. However, when I attempt to import the data, everything goes fine until it hits the data related to the section (weblog) entries. Below is an example error message I’m getting, along with the data that’s causing the error.

Anyone have experience doing this, and is there anything I’m missing or overlooking? When I’m exporting from PHPMyAdmin, I’m choosing 4.0 for MySQL Export Compatibility, which I thought would be enough.

[ERROR in query 50] You have an error in your SQL syntax.  Check the manual that corresponds to your MySQL server version for the right syntax to use near ''a:21:{s:9:"weblog_id";s:1:"2";s:8:"entry_id";s:1:"2";s:9:"auth

Any help is greatly appreciated, as I am at the end of my rope on this one.

It’s choking on the serialized array.  Hm- ok, make sure you’re not running in strict mode (I doubt it’s related to this- but double check anyway).  Then I think I would clear all caches in ‘Admin- Utilities’- that’s going to empty out those arrays.  They’ll repopulate on browser load, so that shouldn’t be a problem.  Export and see if it will take it then.

You may still run into a problem with the exp_sites table- it holds serialized arrays as well.  But let’s see if we can get the relationship table in there.

And I’m going to give the crew a ‘heads up’ on this one- it’s something we’ll want to make note of if it’s a general rather than site specific issue.  And I’m just not sure on that one at the moment.

Robin,

Thanks for the quick response - I’ll try what you mentioned and report back. I’ll also see if the new hosting is running in Strict Mode (I’m assuming you’re talking about PHP).

LOL - I was logged in as my client by accident, and replied - anyways, I’ll let you know how things go!

Sorry for the lack of clarity- it’s the MySQL server that can’t be in strict mode (it’s in the requirements).  PHP- I don’t recall issues.  I’m not a fan of safe mode, but strict mode…  I don’t recall any issues.  I can ask just for clarification (need to send an ‘alert’ on this thread anyway), but it’s not going to jam up an import and it’s not noted in the docs.  Should be fine.