• Dear readers,

    I created a webshop and want to migrate it to blue host before putting any more time in it. I created wordpress at my blue host account and removed all the content that the new database contained so I can start fresh. But I get a error when importing the mysql.sql file, the error is the following:

    #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 ‘STATS_PERSISTENT=0’ at line 16

    Here does the error come from:

    REATE TABLE IF NOT EXISTS innodb_index_stats (
    database_name varchar(64) COLLATE utf8_bin NOT NULL,
    table_name varchar(64) COLLATE utf8_bin NOT NULL,
    index_name varchar(64) COLLATE utf8_bin NOT NULL,
    last_update timestamp NOT NULL DEFAULT CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP,
    stat_name varchar(64) COLLATE utf8_bin NOT NULL,
    stat_value bigint(20) unsigned NOT NULL,
    sample_size bigint(20) unsigned DEFAULT NULL,
    stat_description varchar(1024) COLLATE utf8_bin NOT NULL
    ) ENGINE=InnoDB DEFAULT CHARSET=utf8 COLLATE=utf8_bin STATS_PERSISTENT=0;
    REATE TABLE IF NOT EXISTS innodb_index_stats (
    database_name varchar(64) COLLATE utf8_bin NOT NULL,
    table_name varchar(64) COLLATE utf8_bin NOT NULL,
    index_name varchar(64) COLLATE utf8_bin NOT NULL,
    last_update timestamp NOT NULL DEFAULT CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP,
    stat_name varchar(64) COLLATE utf8_bin NOT NULL,
    stat_value bigint(20) unsigned NOT NULL,
    sample_size bigint(20) unsigned DEFAULT NULL,
    stat_description varchar(1024) COLLATE utf8_bin NOT NULL
    ) ENGINE=InnoDB DEFAULT CHARSET=utf8 COLLATE=utf8_bin STATS_PERSISTENT=0;

    Why am I getting the error?

Viewing 4 replies - 1 through 4 (of 4 total)
  • This is most likely due to your local database version being different from bluehost. What are both versions?

    Thread Starter BrainUpgrade

    (@brainupgrade)

    Thanks for the reply!
    But they are both on the exact same version unfortunately, this is the version.php from both my local and original (unedited) Bluehost ”wp-includes” folder.

    <?php
    /**
    * The WordPress version string
    *
    * @global string $wp_version
    */
    $wp_version = ‘4.0’;

    /**
    * Holds the WordPress DB revision, increments when changes are made to the WordPress DB schema.
    *
    * @global int $wp_db_version
    */
    $wp_db_version = 29630;

    /**
    * Holds the TinyMCE version
    *
    * @global string $tinymce_version
    */
    $tinymce_version = ‘4104-20140822’;

    /**
    * Holds the required PHP version
    *
    * @global string $required_php_version
    */
    $required_php_version = ‘5.2.4’;

    /**
    * Holds the required MySQL version
    *
    * @global string $required_mysql_version
    */
    $required_mysql_version = ‘5.0’;

    Thread Starter BrainUpgrade

    (@brainupgrade)

    Is it possible it is due to the engine being InnoDB?

    Thread Starter BrainUpgrade

    (@brainupgrade)

    If it is, how do i change the engine from InnoDB to a usable engine?

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘WordPress local (XAMPP) to Bluehost’ is closed to new replies.