#75 utf8 causes failure

closed
nobody
None
5
2013-02-22
2013-02-22
Alex May
No

I have the following problem which was experienced with version 2.5 and not solved by upgrading to 3.0

The backup fails since I changed my compilation to UTF. All the advice seems to be that UTF should be used everywhere and it otherwise seems to work well.

Error log says:
mysqldump: Character set 'uft8' is not a compiled character set and is not specified in the '/usr/share/mysql/charsets/Index.xml' file

But:
mysql> show collation;
+----------------------+----------+-----+---------+----------+---------+
| Collation | Charset | Id | Default | Compiled | Sortlen |
+----------------------+----------+-----+---------+----------+---------+
| utf8_general_ci | utf8 | 33 | Yes | Yes | 1 |

And:
/usr/share/mysql/charsets/Index.xml contains:
<charset name="utf8">
<family>Unicode</family>
<description>UTF-8 Unicode</description>
<alias>utf-8</alias>
<collation name="utf8_general_ci" id="33">
<flag>primary</flag>
<flag>compiled</flag>
</collation>
<collation name="utf8_bin" id="83">
<flag>binary</flag>
<flag>compiled</flag>
</collation>
</charset>

Discussion

  • Chris Janton
    Chris Janton
    2013-02-22

    the error says U F T 8 - that is not the same as U T F 8
    Did you enter something improperly while changing collations?

     
  • Alex May
    Alex May
    2013-02-22

    Very good spot, thanks.
    Yes, this was an error in my.cnf

     
  • Alex May
    Alex May
    2013-02-22

    • status: open --> closed
     
  • Alex May
    Alex May
    2013-02-22

    turned out to be an error in my.cnf