Erreur Requête SQL : database migration

  • Resolved webreaker

    (@webreaker)


    6 years, 1 month ago

    planning to move my WordPress website to a different server vps
    all tables are imported to the new database except this table which gives an error

    CREATE TABLEwpwj_smush_dir_images` (
    id mediumint(9) NOT NULL AUTO_INCREMENT,
    path text COLLATE utf8mb4_unicode_520_ci NOT NULL,
    resize varchar(55) COLLATE utf8mb4_unicode_520_ci DEFAULT NULL,
    lossy varchar(55) COLLATE utf8mb4_unicode_520_ci DEFAULT NULL,
    error varchar(55) COLLATE utf8mb4_unicode_520_ci DEFAULT NULL,
    image_size int(10) unsigned DEFAULT NULL,
    orig_size int(10) unsigned DEFAULT NULL,
    file_time int(10) unsigned DEFAULT NULL,
    last_scan timestamp NOT NULL DEFAULT ‘0000-00-00 00:00:00’,
    meta text COLLATE utf8mb4_unicode_520_ci DEFAULT NULL,
    path_hash char(32) COLLATE utf8mb4_unicode_520_ci DEFAULT NULL,
    UNIQUE KEY id (id),
    UNIQUE KEY path_hash (path_hash),
    KEY image_size (image_size)
    ) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_520_ci`

    MySQL a répondu : Documentation
    #1273 – Unknown collation: ‘utf8mb4_unicode_520_ci’

    The page I need help with: [log in to see the link]

Viewing 4 replies - 1 through 4 (of 4 total)
  • Anton Vanyukov

    (@vanyukov)

    6 years, 1 month ago

    Hi @webreaker,

    You can use the same collation as in other tables. Or you can try “utf8mb4_unicode_ci”

    Best regards,
    Anton

    Thread Starter webreaker

    (@webreaker)

    6 years ago

    I change it to “utf8mb4_unicode_ci” but keep displaying the same error

    Anton Vanyukov

    (@vanyukov)

    6 years ago

    Hi @webreaker,

    Even when you changed it to utf8mb4_unicode_ci it’s complaining about utf8mb4_unicode_520_ci? Those are two different collations… Maybe there are other instances where it’s not changed?

    Best regards,
    Anton

    Plugin Support Imran – WPMU DEV Support

    (@wpmudev-support9)

    5 years, 11 months ago

    Hello @webreaker

    I trust you are doing well!

    We haven’t heard back from you for a while now so we’ve marked this ticket as resolved. If you do have any followup questions or require further assistance feel free to reopen it and let us know here.

    Kind regards,
    Nastia

Viewing 4 replies - 1 through 4 (of 4 total)

The topic ‘Erreur Requête SQL : database migration’ is closed to new replies.