[wp-trac] [WordPress Trac] #58871: support uca14.0.0 collation in database where available

[WordPress Trac]

#58871: support uca14.0.0 collation in database where available
-------------------------------------------------+-------------------------
 Reporter:  danielblack                          |       Owner:  (none)
     Type:  enhancement                          |      Status:  new
 Priority:  normal                               |   Milestone:  Awaiting
                                                 |  Review
Component:  Database                             |     Version:  6.3
 Severity:  normal                               |  Resolution:
 Keywords:  has-patch has-unit-tests needs-      |     Focuses:
  testing needs-refresh                          |  performance
-------------------------------------------------+-------------------------

Comment (by oxfordmetadata):

 My apologies for the misunderstanding in my tone, in my fast and furious
 indeed message.
 But the "performance", or efficiency shall I say, improvement from the
 transition to utf8mb4_uca1400_ai_ci are pretty noticeable (thought I
 cannot really tell if it is more from the new collation itself or from the
 fact that now all objects have the same collation).
 Indeed I was pretty pissed off noticing that our Pods plugin when creating
 Advanced Content Types (in their own tables) kept using unicode_520_ci,
 although the other tables were unicode_ci, leading to the need of explicit
 COLLATE statement mess and so on.
 Earlier today we found that the "culprit" was that piece of code.

 From MariaDB's presentation it appeared to me that these naming
 differences are here to stay, so we have to figure out something that if
 anything, it will maintain all the tables to their existing collation.

 I guess I overstayed my welcome.

 Once more, please accept my apologies.

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