{"push_id":849271078,"size":2,"distinct_size":2,"ref":"refs/heads/master","head":"fb6f0d406bb9c4fed7fb63b91fe67ad209487a5f","before":"10a80e39feb8f5da0ff50f1b04c3f84e7bbbbb54","commits":[{"sha":"322068fe85278ea26e26da6dfd7c5612dab15a72","author":{"email":"bca6f4261a19f75277fe4325de3272d15492eb61@gmail.com","name":"Ryuta Kamizono"},"message":"Remove `DEFAULT_CHARSET` and `DEFAULT_COLLATION` in `MySQLDatabaseTasks`\n\nThis reverts commit f6ca7e4e75408bc42f515fc7206d6c6ff0dce7c6.\n\nThe default collation of utf8 in MySQL is the `utf8_general_ci`, and\nthis should not be changed. This is because, the better collation in the\nall locales is not exists, optimal collation in own application is not\nknown other than themselves.\n\nThe `utf8_unicode_ci` is known as Japanese killer in Japan, there are\nserious impacts in search of Japanese.\n\nMySQL implements the `utf8_unicode_ci` according to the Unicode\nCollation Algorithm (UCA) described at http://www.unicode.org/reports/tr10/,\nbut the `utf8_unicode_ci` have only partial support for the UCA, only\nprimary level key comparison implemented (also known as L1 (Base\ncharacters) comparison).\n\nBecause L1 (Base characters) comparison does not distinguish between the\npresence or absence of the accent, if distinction of the accent is\nimportant there is a serious impact (e.g. Japanese).\n\nExample:\n\n```\n> SHOW CREATE TABLE `dicts`\\G\n*************************** 1. row ***************************\n       Table: dicts\nCreate Table: CREATE TABLE `dicts` (\n  `word` varchar(255) COLLATE utf8_unicode_ci DEFAULT NULL,\n  `meaning` varchar(255) COLLATE utf8_unicode_ci DEFAULT NULL\n) ENGINE=InnoDB DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci\n1 row in set (0.00 sec)\n\n> INSERT INTO `dicts` VALUES ('ハハ', 'mother'), ('パパ', 'father');\nQuery OK, 2 rows affected (0.00 sec)\n\n> SELECT * FROM `dicts` WHERE `word` = 'ハハ';\n+--------+---------+\n| word   | meaning |\n+--------+---------+\n| ハハ   | mother  |\n| パパ   | father  |\n+--------+---------+\n2 rows in set (0.00 sec)\n\n> CREATE UNIQUE INDEX `unique_index_word` ON `dicts`(`word`);\nERROR 1062 (23000): Duplicate entry 'ハハ' for key 'unique_index_word'\n```\n\nWe should omit the collation entirely rather than providing a default.\nThen the choice is the responsibility of the server and MySQL distribution.","distinct":true,"url":"https://api.github.com/repos/rails/rails/commits/322068fe85278ea26e26da6dfd7c5612dab15a72"},{"sha":"fb6f0d406bb9c4fed7fb63b91fe67ad209487a5f","author":{"email":"378ef3e7f140926a1b45e233cf8a3a5b6f1bde10@users.noreply.github.com","name":"Andrew White"},"message":"Merge pull request #22061 from kamipo/remove_default_charset_and_collation\n\nRemove `DEFAULT_CHARSET` and `DEFAULT_COLLATION`","distinct":true,"url":"https://api.github.com/repos/rails/rails/commits/fb6f0d406bb9c4fed7fb63b91fe67ad209487a5f"}]}