Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>In general, <em>utf8_general_ci</em> is faster than <em>utf8_unicode_ci</em>, but less correct.</p> <p>Here is the difference:</p> <blockquote> <p>For any Unicode character set, <strong>operations performed using the _general_ci collation are faster than those for the _unicode_ci collation</strong>. For example, comparisons for the utf8_general_ci collation are faster, but slightly less correct, than comparisons for utf8_unicode_ci. The reason for this is that utf8_unicode_ci supports mappings such as expansions; that is, when one character compares as equal to combinations of other characters. For example, in German and some other languages “ß” is equal to “ss”. utf8_unicode_ci also supports contractions and ignorable characters. utf8_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. </p> </blockquote> <p>Quoted from: <a href="http://dev.mysql.com/doc/refman/5.0/en/charset-unicode-sets.html" rel="noreferrer">http://dev.mysql.com/doc/refman/5.0/en/charset-unicode-sets.html</a></p> <p>For more detailed explanation, please read the following post from MySQL forums: <a href="http://forums.mysql.com/read.php?103,187048,188748" rel="noreferrer">http://forums.mysql.com/read.php?103,187048,188748</a></p> <p>As for utf8_bin: Both <em>utf8_general_ci</em> and <em>utf8_unicode_ci</em> perform case-insensitive comparison. In constrast, <strong>utf8_bin is case-sensitive</strong> (among other differences), because it compares the binary values of the characters.</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload