Since then, upstream has fixed that bug by introducing identical (as checked on 5.6) but differently-named collations utf8_general_mysql500_ci and ucs2_general50_ci.
Thus, we can remove Percona-specific collations from 5.6. In 5.1/5.5 we can keep them but make them share the definition tables with the upstream siblings.
utf8_general50_ci and ucs2_general50_ci collations were introduced for /blueprints. launchpad. net/percona- server/ +spec/utf8- general50- ci-5.1 /blueprints. launchpad. net/percona- server/ +spec/utf8- general50- ci-5.5
https:/
https:/
in order to fix http:// bugs.mysql. com/bug. php?id= 43593.
Since then, upstream has fixed that bug by introducing identical (as checked on 5.6) but differently-named collations utf8_general_ mysql500_ ci and ucs2_general50_ci.
Thus, we can remove Percona-specific collations from 5.6. In 5.1/5.5 we can keep them but make them share the definition tables with the upstream siblings.