I’ve used admin and wp migrate db tools and still can’t get a clean import. phpMyAdmin reports syntax errors but when I visibly inspect or use syntax validation tools everything looks fine. Another strange thing is that when using adminer vs wp migrate plugin, the syntax error is in 2 totally different tables. I’ve optimized my tables with no errors as well.
wp migrate db error (raw export - change root file path, remove transients, comments and revisions):
#1064 - You have an error in your SQL syntax; check the manual that corresponds to your MariaDB server
version for the right syntax to use near
'INSERT INTO `wp_options` ( `option_id`, `option_name`, `option_value`, `autoload' line 67
when I check this the close brace is there just before passing VALUES(...);
which also has the right syntax.
adminer error (exact raw db export):
#1064 - You have an error in your SQL syntax; check the manual that corresponds to your MariaDB server
version for the right syntax to use near
'jetpack_unique_connection', 'a:3:{s:9:\"connected\";i:1;s:12:\"disconnected\";i:' at line 186
The syntax for this one also looks good.
Heck, even when I export the uncompressed db created by the ee site create script (clean, brand-new db), importing that back in also results in syntax errors. How could this be?
I’m going to try command line import but wondering if someone else has ran into this type of quirk before?