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

[Michel Rodriguez]

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

1: e907b03853 = 1: e907b03853 Support for utf8mb4 in mysql.
2: c58b93935b ! 2: 8c0eb14b13 Explain utf8mb4 character set options.
    @@ -12,6 +12,18 @@
     +    MySQL version 5.7 ( >= 5.7.7, < 5.8)
     +    MariaDB version >= 10.2.5
     +
    ++Before this version utf8mb4 tables could not have indexes with type 
    ++VARCHAR(255): the default size for index entries was 767 bytes, which 
    ++is enough for 255 chars stored as at most 3 chars (the utf8 format), 
    ++but not as 4 bytes (utf8mb4).
    ++
    ++5.7.7/10.2.5 sets the default index size to 3072 for INNODB tables, 
    ++so all of RT indexes are now OK.
    ++
    ++https://dev.mysql.com/doc/relnotes/mysql/5.7/en/news-5-7-7.html#mysqld-5-7-7-feature
    ++https://mariadb.com/kb/en/changes-improvements-in-mariadb-102/
    ++https://mariadb.com/kb/en/mariadb-1025-changelog/ (search for utf8)
    ++    
     +This ensures proper support for the full utf8 character set (utf8mb4).
     +
     +In MySQL, RT uses the utf8mb4 character set, in order to support all
3: aaea69e3a5 = 3: 915e833dea Normalize character set/collation declaration for all tables.
4: f90c748d64 = 4: 1592cfaa25 Test for 4-byte utf-8 character searches.
5: b5f67eb0b7 = 5: d5e9546c59 Change the full text indexer charset to utf8mb4.
6: 211c586375 = 6: f0c010800e Alter all relevant tables to use the utf8mb4 charset.
7: 8e2c13e559 = 7: 35e9930253 Remove check on innodb_log_file_size.