Comments on: Moving Hosts + MySQL Errors

By: gofree

gofree — Thu, 07 Feb 2008 06:08:05 +0000

How about adding compatibility when you export your database:

SQL compatibility mode: MYSQL40
Check this: Add IF NOT EXISTS

I export and import without any issue.

Correct me if m wrong.

By: JB

JB — Mon, 30 Jul 2007 11:15:33 +0000

Change

“timestamp NOT NULL default CURRENT_TIMESTAMP on update CURRENT_TIMESTAMP,”

“timestamp(14) NOT NULL,”

By: Ron

Ron — Fri, 10 Nov 2006 10:04:36 +0000

Hi,

Interesting! I have a big problem with:

#1064 – 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 ‘CURRENT_TIMESTAMP on update CURRENT_TIMESTAMP,

Does anybody know a sollution??? I’m desperate with als a big headache

By: Aegilops

Aegilops — Sat, 11 Mar 2006 16:44:56 +0000

Can someone please give MrBister a mountain of gold or something, as that –compatible switch has just saved me from going bonkers.

Was going from a 4.1 (Gentoo Linux) to a 4.0 (OpenBSD 3.8) and was getting very bogged down with some dodgy syntax issues.

Thank you!

Aegilops

By: Terry

Terry — Sat, 17 Dec 2005 15:43:51 +0000

Thank you for posting that MrBister

By: MrBister

MrBister — Fri, 16 Dec 2005 11:51:13 +0000

I found a solution that you can use if you are able to run mysqldump at the server itself:

“mysqldump -u username -ppassword –compatible=mysql40 database_name >FILENAME.sql”

–compatible=mysql40 makes it compatible with older versions.

The above worked for me to remove the annoying DEFAULT CHARSET problem

By: Terry

Terry — Fri, 09 Sep 2005 05:56:43 +0000

Thanks for the info Peter – too much headache for lazy me though!

I actually did try removing the DEFAULT CHARSET=latin1 line and I ended up with funky character encoding issues on the web copy. *What a mess*.

hmmm but now that I know you know this MySQL stuff, and where to find you , methinks you should hide .

By: Peter Cooper

Peter Cooper — Thu, 08 Sep 2005 13:32:08 +0000

It’s do-able, but you have to hack a few things out of your MySQL dump

For example, MySQL 4.0 doesn’t support the “DEFAULT CHARSET=latin1″ stuff. You can also drop all the DISABLE or ENABLE KEYS lines.