4번독수리의 둥지
_general_ci Versus _unicode_ci Collations 본문
https://dev.mysql.com/doc/refman/8.0/en/charset-unicode-sets.html
For any Unicode character set, operations performed using the xxx_general_ci collation are faster than those for the xxx_unicode_ci collation. For example, comparisons for the utf8mb4_general_ci collation are faster, but slightly less correct, than comparisons for utf8mb4_unicode_ci. The reason is that utf8mb4_unicode_ci supports mappings such as expansions; that is, when one character compares as equal to combinations of other characters. For xample,
ß is equal to ss in German and some other languages. utf8mb4_unicode_ci also supports contractions and ignorable characters. utf8mb4_general_ci is a legacy collation that does not support expansions, contractions, or ignorable characters. It can make only one-to-one comparisons between characters.
https://rastalion.me/mysql-8-0-1-버전부터-채택된-utf8mb4_0900_ai_ci의-한글-사용에-대한-문제점/
utf8mb4_0900_ai_ci에서 "가"와 "ㄱㅏ"를 같은 문자열로 판정한다는 글.
'Database > MySQL' 카테고리의 다른 글
| MySQL Covering index (0) | 2017.09.19 |
|---|---|
| MySQL DATE_ADD() vs php strtotime() (0) | 2016.09.21 |
| SQL JOIN (0) | 2016.02.24 |
| Select tables optimized away (0) | 2015.10.23 |
| Correct indexing when using OR operator (0) | 2015.09.08 |