Why utf8_general_ci collation?

  • Nazar Hotsa

    (@bugnumber9)


    4 years ago

    Hi Gioni,

    Happy Easter!

    I noticed that all WP Cerber tables are getting created with utf8_general_ci collation on our servers.
    Which is weird since DB_CHARSET is set to utf8mb4 in wp-config file, the database itself uses utf8mb4_unicode_ci collation, all standard WP tables are getting created with utf8mb4_unicode_520_ci collation.

    So I started digging into the code and noticed that cerber_create_db function doesn’t specify any collation at all. At the same time you have nexus_create_db function which specifies both charset and collation based on checks, which is great.

    That being said, I believe it makes sense to adjust cerber_create_db function to be similar to nexus_create_db in terms of choosing charset and collation, what do you think?

    Cheers!

Viewing 1 replies (of 1 total)
  • Plugin Author gioni

    (@gioni)

    4 years ago

    Hi! You too!

    Yes, the plugin uses UTF8 from day one. Although the plugin doesn’t need any particular encoding to be set to protect a website, you’re right, that should and will be improved. I wonder what really forces you to use DB_CHARSET to enforce using utf8mb4?

Viewing 1 replies (of 1 total)
  • The topic ‘Why utf8_general_ci collation?’ is closed to new replies.