• Resolved bg17aw

    (@bg17aw)


    Probably you are already familiar with this issue, “Utf8mb4_unicode_520_ci” is not supported on some MYSQL versions.

    Can you add a fix in Duplicator for this? Could be something as simple as a checkbox to export all tables using “Utf8mb4_unicode_ci” collation.

    Thank you!

Viewing 3 replies - 1 through 3 (of 3 total)
  • Hey @bg17aw,

    Thanks for the feedback! The only work-a-rounds we have at the moment are in this FAQ.

    ? ? – What is Compatibility mode & ‘Unknown collation’ errors?
    ? ? – https://snapcreek.com/duplicator/docs/faqs-tech/#faq-installer-110-q

    The underlying issue with changing the collation type from one server to the next is that you can cause data loss. In order to maintain the highest integrity of the data its best to keep the collations the same during a move which means trying to have mysql server versions close together between the build and install servers.

    Hope that helps~

    Let me know if any of them help~

    Thread Starter bg17aw

    (@bg17aw)

    Thanks for your answer,

    Not sure if there would be data loss between Utf8mb4_unicode_520_ci and Utf8mb4_unicode_ci though.

    Personally, I just open the database.sql file from the Duplicator archive and search/replaced all occurrences of Utf8mb4_unicode_520_ci with Utf8mb4_unicode_ci.

    Although I understand your concern, but I think it would help a lot of users (looking at the huge number of Google Search hits for this issue) if you would implement a checkbox somewhere in the “Advanced” options, and display a warning about possible data loss. 99.9% of the cases there would be no data loss, the user was warned etc.

    Thanks

    I’ll add the task to the backlog to see if we can come up with a solution like that.

    Thanks for the feedback!

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘The Utf8mb4_unicode_520_ci error’ is closed to new replies.