Databases
StackOverflow2013
Postsdbo
POWhy is MySQL treating é the same as e?
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POWhy is MySQL treating é the same as e?
    primarykey
    data
    text
    <p>I'm storing Unicode strings in a MySQL database with a Django web application. I can store Unicode data fine, but when querying, I find that <code>é</code> and <code>e</code> are treated as if they were the same character:</p> <pre><code>In [1]: User.objects.filter(last_name='Jildén') Out[1]: [&lt;User: Anders Jildén&gt;] In [2]: User.objects.filter(last_name='Jilden') Out[2]: [&lt;User: Anders Jildén&gt;] </code></pre> <p>This is also the case when using the MySQL shell directly:</p> <pre><code>mysql&gt; select last_name from auth_user where last_name = 'Jildén'; +-----------+ | last_name | +-----------+ | Jildén | +-----------+ 1 row in set (0.00 sec) mysql&gt; select last_name from auth_user where last_name = 'Jilden'; +-----------+ | last_name | +-----------+ | Jildén | +-----------+ 1 row in set (0.01 sec) </code></pre> <p>Here are the database charset settings:</p> <pre><code>mysql&gt; SHOW variables LIKE '%character_set%'; +--------------------------+------------------------------------------------------+ | Variable_name | Value | +--------------------------+------------------------------------------------------+ | character_set_client | latin1 | | character_set_connection | latin1 | | character_set_database | utf8 | | character_set_filesystem | binary | | character_set_results | latin1 | | character_set_server | latin1 | | character_set_system | utf8 | | character_sets_dir | /usr/local/Cellar/mysql/5.1.54/share/mysql/charsets/ | +--------------------------+------------------------------------------------------+ </code></pre> <p>here's the table schema:</p> <pre><code>CREATE TABLE `auth_user` ( `id` int(11) NOT NULL AUTO_INCREMENT, `username` varchar(30) CHARACTER SET utf8 NOT NULL, `first_name` varchar(30) CHARACTER SET utf8 NOT NULL, `last_name` varchar(30) CHARACTER SET utf8 NOT NULL, `email` varchar(200) CHARACTER SET utf8 NOT NULL, `password` varchar(128) CHARACTER SET utf8 NOT NULL, `is_staff` tinyint(1) NOT NULL, `is_active` tinyint(1) NOT NULL, `is_superuser` tinyint(1) NOT NULL, `last_login` datetime NOT NULL, `date_joined` datetime NOT NULL, PRIMARY KEY (`id`), UNIQUE KEY `username` (`username`) ) ENGINE=InnoDB AUTO_INCREMENT=7952 DEFAULT CHARSET=utf8 COLLATE=utf8_bin </code></pre> <p>and here are the options I'm passing via Django's <code>DATABASES</code> setting:</p> <pre><code>DATABASES = { 'default': { # ... 'OPTIONS': { 'charset': 'utf8', 'init_command': 'SET storage_engine=INNODB;', }, }, } </code></pre> <p>Note that I have tried setting the table collation to <code>utf8_bin</code>, with no effect:</p> <pre><code>mysql&gt; alter table auth_user collate utf8_bin; mysql&gt; select last_name from auth_user where last_name = 'Jilden'; +-----------+ | last_name | +-----------+ | Jildén | +-----------+ 1 row in set (0.00 sec) </code></pre> <p>How can I get MySQL to treat these as different characters?</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USnulll
    1. USclaymation
    plurals
    1. This table or related slice is empty.
    1. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    3. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POWhy is MySQL treating é the same as e?
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POWhy is MySQL treating é the same as e?
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POWhy is MySQL treating é the same as e?
      1. This table or related slice is empty.
      1. VTUpMod
    1. COPlease post the output of `SHOW CREATE TABLE tablename`, where `tablename` is the name of the table containing the relevant column.
      singulars
      1. POWhy is MySQL treating é the same as e?
      1. USHammerite
    2. COI've edited the question to include the table schema. Thanks.
      singulars
      1. POWhy is MySQL treating é the same as e?
      1. USclaymation
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

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