WordPress.org

Ready to get started?Download WordPress

Forums

MySQL Error #1064 (5 posts)

  1. cookiedude
    Member
    Posted 8 years ago #

    Hi all,
    I moved hosts and tried to import my WP database into a freshly set up database on the host, but I got the following error:
    CREATE TABLE wp_categories (
    cat_ID bigint( 20 ) NOT NULL AUTO_INCREMENT ,
    cat_name varchar( 55 ) COLLATE utf8_unicode_ci NOT NULL default '',
    category_nicename varchar( 200 ) COLLATE utf8_unicode_ci NOT NULL default '',
    category_description longtext COLLATE utf8_unicode_ci NOT NULL ,
    category_parent int( 4 ) NOT NULL default '0',
    PRIMARY KEY ( cat_ID ) ,
    KEY category_nicename ( category_nicename )
    ) ENGINE = MYISAM DEFAULT CHARSET = utf8 COLLATE = utf8_unicode_ci AUTO_INCREMENT =15;
    #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 'collate utf8_unicode_ci NOT NULL default '',category_nicen

    Does anyone know what to with this? I'm writing in German on my blog and have had trouble with importing databases before, due to issues with character encoding. Looks like it's something along those lines again.

    Oh, and one more thing: I searched the forum and found another thread dealing with MySQL Error #1064, but the solution offered there doesn't seem to apply to my case, or at least I wouldn't know how to and the topic was labelled as resolved. The FAQ doesn't seem to say anything about posting or not posting in resolved threads. I did see however you can filter search results for resolved/unresolved, so this is merely to make sure I have not posted in the wrong location. Please don't take this as spamming or bumping, I know how annoying this can be from other forums. Thanks :)

  2. ticklecove
    Member
    Posted 8 years ago #

    I think you may have the same problem I did, which was moving between different versions of mySQL. I was using mySQL 4.1 on my staging machine and didn't pay attention to the fact that my hosting provider was on mySQL 3.23. There are syntax and reserved word differences between the versions.

    I resolved this issue by exporting the database a second time using the SQL export compatility mode and reimporting again on the new target host. If you are using phpMyAdmin, you can set the "SQL export compatibility:" dropdown box to "MYSQL323" or "MYSQL40", etc.

    Ich hoffe es hilft,
    Jeff

  3. SteveO
    Member
    Posted 8 years ago #

    You rock, Jeff! This was kicking my butt, mentally speaking. I should have known to check here.

    Danke schoen :)
    Steve

  4. nicknormal
    Member
    Posted 7 years ago #

    jeff,
    double-rock! i was in search for this answer, this thread helped a lot. simple=effective. cheers.
    Nick

  5. duckster
    Member
    Posted 7 years ago #

    Alllllright! Way to go! I was having the same issues!!!! Wonderbubble!

    Mine was as small a discrepancy as trying to export from 4.026 to 4.027, but it wasn't working until I told it to export as 4.0.

Topic Closed

This topic has been closed to new replies.

About this Topic