List:General Discussion« Previous MessageNext Message »
From:Gleb Paharenko Date:July 19 2005 8:12am
Subject:Re: Illegal mix of collations
View as plain text  
Hello.


>  `key` varchar(255) character set utf8 collate utf8_bin NOT NULL
																^^^^^^^^^^^^^^^

Field's character set should be latin1 as well. Change it.





> 
> The default charset of the slave table is latin1, the same on the
> master.
> 
> Slave Table create statement:
> =============================
> CREATE TABLE `sum_day_key_requests` (
> ...
>  `key` varchar(255) character set utf8 collate utf8_bin NOT NULL
> default '',
> ...
> ) ENGINE=InnoDB DEFAULT CHARSET=latin1;
> 
> which is identical with the Master create statement:
> 
> CREATE TABLE `sum_day_key_requests` (
>  ...
>  `key` varchar(255) character set utf8 collate utf8_bin NOT NULL
> default '',
> ...
> ) ENGINE=InnoDB DEFAULT CHARSET=latin1;
> 
> Marco
> 
> ----
> Marco Poehler
> http://www.kontaktlinsen-preisvergleich.de
> 
> Am Montag, den 18.07.2005, 21:34 +0300 schrieb Gleb Paharenko:
> 
> 


-- 
For technical support contracts, goto https://order.mysql.com/?ref=ensita
This email is sponsored by Ensita.NET http://www.ensita.net/
   __  ___     ___ ____  __
  /  |/  /_ __/ __/ __ \/ /    Gleb Paharenko
 / /|_/ / // /\ \/ /_/ / /__   Gleb.Paharenko@stripped
/_/  /_/\_, /___/\___\_\___/   MySQL AB / Ensita.NET
       <___/   www.mysql.com



Thread
Illegal mix of collationsMarco Pöhler18 Jul
  • Re: Illegal mix of collationsGleb Paharenko18 Jul
    • Re: Illegal mix of collationsMarco Pöhler19 Jul
      • Re: Illegal mix of collationsGleb Paharenko19 Jul