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

Michel Rodriguez michel at bestpractical.com
Tue Dec 10 08:26:59 EST 2019


The branch 4.6/mysql-utf8mb4 was deleted and repushed:
       was 1d8d4df7914fe7c791b4cf199764ad552e580da0
       now cf02e1942061458b61a7bb49a4e072b5fd25ee33

1: 09ab7e5891 ! 1: b6ab972188 Support for utf8mb4 in mysql.
    @@ -1,6 +1,6 @@
     Author: michel <michel at bestpractical.com>
     
    -    Adds support for utf8mb4 in mysql.
    +    Support for utf8mb4 in mysql.
         
         This allows 4-byte characters, such as emojis, in fields.
         This feature is supported in mysql 5.5.3 and later.
2: e53879581d ! 2: dd950130cf Check that the database charset is utf8mb4.
    @@ -1,6 +1,6 @@
     Author: michel <michel at bestpractical.com>
     
    -    Adds check on the database encoding. It should be utf8mb4.
    +    Check that the database charset is utf8mb4.
         
         We check one column (Tickets.Subject) for practical reasons.
     
3: 46baf3d45c ! 3: f1b780f45c Explain utf8mb4 character set options.
    @@ -1,6 +1,6 @@
     Author: michel <michel at bestpractical.com>
     
    -    Adds README.MySQL to explain utf8mb4 character set options.
    +    Explain utf8mb4 character set options.
     
     diff --git a/README.MySQL b/README.MySQL
     new file mode 100644
4: f9c6adedad ! 4: 2079d9171d Normalize character set/collation declaration for all tables.
    @@ -1,8 +1,6 @@
     Author: michel <michel at bestpractical.com>
     
    -    Normalizes character set/collation declaration for all tables.
    -    
    -    to "CHARACTER SET = utf8mb4 COLLATE = utf8mb4_unicode_ci
    +    Normalize character set/collation declaration for all tables.
     
     diff --git a/etc/schema.mysql b/etc/schema.mysql
     --- a/etc/schema.mysql
5: b9e5c51ea3 ! 5: e9a2e77979 Test for 4-byte utf-8 character searches.
    @@ -1,6 +1,6 @@
     Author: michel <michel at bestpractical.com>
     
    -    Adds test for 4-byte utf-8 character searches.
    +    Test for 4-byte utf-8 character searches.
         
         Mostly to check that MySQL does the right thing with them, using
         the utf8mb4 character set.
6: 82ce30b66d ! 6: 7d57f69715 Change the full text indexer charset to utf8mb4.
    @@ -1,8 +1,8 @@
     Author: michel <michel at bestpractical.com>
     
    -    Adds the utf8mb4 character set to the full text indexer
    +    Change the full text indexer charset to utf8mb4.
         
    -    Without this the indexer fails on 4-byte utf8 characters
    +    Without this the indexer fails on 4-byte utf8 characters.
         Note that full test searches do not find emojis, since they are not words.
     
     diff --git a/sbin/rt-setup-fulltext-index.in b/sbin/rt-setup-fulltext-index.in
7: 1d8d4df791 ! 7: 913b006f98 Alter all relevant tables to use the utf8mb4 charset.
    @@ -1,6 +1,6 @@
     Author: michel <michel at bestpractical.com>
     
    -    Adds the upgrade script: alters all relevant tables to use the utf8mb4 charset.
    +    Alter all relevant tables to use the utf8mb4 charset.
         
         The data itself should not change: it doesn't include any 4 byte utf8 character.
     
    @@ -31,3 +31,4 @@
     + ALTER TABLE `Assets` CONVERT TO CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_ci;
     + ALTER TABLE `Catalogs` CONVERT TO CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_ci;
     + ALTER TABLE `CustomRoles` CONVERT TO CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_ci;
    +
-:  ------- > 8: cf02e19420 Improve mysql/mariadb version checks.



More information about the rt-commit mailing list