UTF-8 and remote mysql clients : collation conflict

  • hendrikjan

    (@hendrikjan)


    16 years, 10 months ago

    Just a warning:

    if you install a fresh WP, the table definitions (SQL) do provide UTF-8 as type, but they do not include UTF-8 as collation. If your server is default set to latin charsets, this can lead to UTF-8 tables and LATIN columns.

    Some SQL clients do get confused and could ruin your data.

    It would be very nice if the installer/upgrader of WP explicitely indicates fields being UTF-8 by adding

    COLLATE utf8_general_ci

    to their sql.

    What are your thoughts?

Viewing 1 replies (of 1 total)
  • MichaelH

    (@michaelh)

    16 years, 10 months ago

    That was done intentionally by the developers (i.e. leaving DB_COLLATE set to ”).

    The Trac ticket 3517 has the complete story.

    If you believe developers should change their thinking on that, I would recommend either starting a new ticket in trac (refer to ticket 3517), or join and post your thoughts to the wp-hackers email list.

    Resources:
    Reporting_Bugs
    Mailing_Lists

Viewing 1 replies (of 1 total)
  • The topic ‘UTF-8 and remote mysql clients : collation conflict’ is closed to new replies.