[wp-trac] [WordPress Trac] #37956: DB_COLLATE doesn't override $collate when defining utf8mb4_unicode_ci in wp-config

[WordPress Trac]

#37956: DB_COLLATE doesn't override $collate when defining utf8mb4_unicode_ci in
wp-config
--------------------------+-----------------------
 Reporter:  MikeGillihan  |       Owner:
     Type:  defect (bug)  |      Status:  reopened
 Priority:  normal        |   Milestone:
Component:  Database      |     Version:  4.6
 Severity:  normal        |  Resolution:
 Keywords:                |     Focuses:
--------------------------+-----------------------
Changes (by cjke7777):

 * status:  closed => reopened
 * resolution:  wontfix =>


Comment:

 I want to echo the sentiment here, that WP should be respecting the
 DB_COLLATE/DB_CHARSET if explicitly set.

 There is an open bug in mysql where  utf8mb4_unicode_520_ci doesn't
 correctly distinguish certain Japanese characters
 (https://bugs.mysql.com/bug.php?id=79977).

 So when I use `get_page_by_title` in Wordpress with a dakuten, it will
 incorrectly return  a result if they share a base (searching for ぺ will
 return a post with へ). Simple solution is to not use the 520 collation.

 It would be ok to say it's a bug in mysql (which is true), but I should be
 able to select the best charset/collate for my particular use case.

--
Ticket URL: <https://core.trac.wordpress.org/ticket/37956#comment:4>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform