[Rt-commit] rt branch, 4.6/mysql-utf8mb4, repushed

[Michel Rodriguez]

The branch 4.6/mysql-utf8mb4 was deleted and repushed:
       was edd56d1fc2195f732b2906f854decc3a57e0ff92
       now 8e2c13e559409c9af9d9dfb49a53911ec136fb9e

1: e907b03853 = 1: e907b03853 Support for utf8mb4 in mysql.
2: dc10bd7cb2 ! 2: c58b93935b Explain utf8mb4 character set options.
    @@ -7,6 +7,13 @@
     --- /dev/null
     +++ b/README.MySQL
     @@
    ++The supported versions of MySQL / MariaDB are;
    ++
    ++    MySQL version 5.7 ( >= 5.7.7, < 5.8)
    ++    MariaDB version >= 10.2.5
    ++
    ++This ensures proper support for the full utf8 character set (utf8mb4).
    ++
     +In MySQL, RT uses the utf8mb4 character set, in order to support all
     +unicode characters, including the ones that are encoded on 4 bytes in
     +utf8 (some Kanji characters and a good number of emojis).
3: aa9470064f = 3: aaea69e3a5 Normalize character set/collation declaration for all tables.
4: c226aa07aa = 4: f90c748d64 Test for 4-byte utf-8 character searches.
5: a326b39593 = 5: b5f67eb0b7 Change the full text indexer charset to utf8mb4.
6: edd56d1fc2 ! 6: 211c586375 Alter all relevant tables to use the utf8mb4 charset.
    @@ -38,3 +38,4 @@
     + ALTER TABLE `Catalogs` CONVERT TO CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_ci;
     + ALTER TABLE `CustomRoles` CONVERT TO CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_ci;
     + ALTER TABLE `ObjectCustomRoles` CONVERT TO CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_ci;
    +
-:  ------- > 7: 8e2c13e559 Remove check on innodb_log_file_size.