MySQL: Pitfalls of using utf8_bin COLLATE?

Question

MySQL

There was a need to build a unique index on a varchar field. An error occurred when adding such an index, because the field uses utf8_general_ci by default and is case insensitive. If you use utf8_bin, then everything is ok.
So what are the pitfalls of using utf8_bin COLLATE? Would it be faster to SELECT on such a field?
Thank you.

Answer 1

When using utf8_bin, the term comparison will occur without normalization. It is logical that the comparison is faster, since there is no normalization.
Details here - https://dev.mysql.com/doc/refman/5.5/en/charset-un...