Ad Widget

Collapse

DB upgrade error from 1.8 to 2.0 (collation mix issue with UTF8)

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • scheuri
    Junior Member
    • Jun 2012
    • 7

    #1

    DB upgrade error from 1.8 to 2.0 (collation mix issue with UTF8)

    Hi all

    I receive an error when patching my 1.8.3 MySQL database with the 2.0.0 patch.sql:
    Code:
    ERROR 1267 (HY000) at line 860: Illegal mix of collations (utf8_general_ci,IMPLICIT) and (utf8_unicode_ci,IMPLICIT) for operation '='

    I made sure that MySQL is running all in UTF8


    Code:
    mysql> SHOW VARIABLES LIKE 'char%';
    +--------------------------+----------------------------+
    | Variable_name            | Value                      |
    +--------------------------+----------------------------+
    | character_set_client     | utf8                       |
    | character_set_connection | utf8                       |
    | character_set_database   | utf8                       |
    | character_set_filesystem | binary                     |
    | character_set_results    | utf8                       |
    | character_set_server     | utf8                       |
    | character_set_system     | utf8                       |
    | character_sets_dir       | /usr/share/mysql/charsets/ |
    +--------------------------+----------------------------+
    8 rows in set (0.00 sec)
    
    mysql> SHOW VARIABLES LIKE '%COLLATION%';
    +----------------------+-----------------+
    | Variable_name        | Value           |
    +----------------------+-----------------+
    | collation_connection | utf8_general_ci |
    | collation_database   | utf8_general_ci |
    | collation_server     | utf8_general_ci |
    +----------------------+-----------------+
    3 rows in set (0.00 sec)
    I am wondering if someone else got that issue and if so, got a solution to that.
    So far I have no idea how to make my database being unicode rather than general, but I am a little surprised that this could cause an issue.

    Thanks a lot for your help
    Best regards
    Stefan
  • scheuri
    Junior Member
    • Jun 2012
    • 7

    #2
    Really no one got that issue?

    Regards
    Scheuri

    Comment

    • scheuri
      Junior Member
      • Jun 2012
      • 7

      #3
      I just tried the same with the patch.sql of 2.0.1.
      Unfortunately it didnt work. Exact same error.

      What I did:
      • Dumping the DB on 1.8.3
      • Importing into new DB (with UTF8 checked)
      • Using patch.sql of 2.0.0 and now 2.0.1


      It does not work.
      Anyone else that issue? Any solution?

      Cheers
      scheuri

      Comment

      Working...