[wp-trac] [WordPress Trac] #45697: Database: Upgrading field collations

[WordPress Trac]

#45697: Database: Upgrading field collations
-------------------------+-----------------------------
 Reporter:  pento        |       Owner:  (none)
     Type:  enhancement  |      Status:  new
 Priority:  normal       |   Milestone:  Future Release
Component:  Database     |     Version:
 Severity:  normal       |  Resolution:
 Keywords:               |     Focuses:
-------------------------+-----------------------------

Comment (by johnjamesjacoby):

 Running into this already, though I'm able to work around it manually for
 the time being.

 Relatedly, it is not uncommon to run into plugins that have not moved to
 `utf8mb4` yet, resulting in collections of tables with varying character
 sets and collations, but I think it's rare that plugins `JOIN` their own
 tables with core ones.

 `[rant]`
 I believe plugins should be responsible for their own database tables, but
 I wish WordPress came with more robust tools to help plugins take on that
 responsibility in a more uniform way.

 BerlinDB versions individual tables with an option for each, and upgrade
 routines run automatically when tables are out of date. They run their own
 character set and collation changes like any other upgrade. It's cheap and
 effective.

 Plugins probably should not be JOINing with WordPress core tables, as
 there is no guarantee all of the tables will be on the same database
 server and accessible to each other.
 `[/rant]`

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