• unknown's avatar
    bug#29562 default collation of ucs2_unicode_ci crashes slave · 7ed59639
    unknown authored
    Problem: some pieces of code relied on the default character
    set settings, which didn't work in case of default character set
    ucs2.
    Fix: Specifying character set explicitly, not to depend on
    the default settings.
    
    
    mysql-test/suite/rpl_ndb/r/rpl_ndb_ctype_ucs2_def.result:
      Recording correct test result
    mysql-test/suite/rpl_ndb/t/disabled.def:
      Enabling test
    sql/ha_ndbcluster_binlog.cc:
      Character set of the NDB helper tables should
      not rely of the default settings, to avoid creating
      tables in different character sets on master and slave.
      Adding explicit character set. UTF8 should be fine.
      
      character_set_client should not rely on the default
      character set settings, which can be ucs2. Helper SQL queries
      sent by NDB are all in pure ASCII. Setting client_character_set
      to latin1.
    sql/log_event.cc:
      Adding assert to make sure that binary log does not have 
      queries in character set which parser does not understand
      (e.g. ucs2).
    7ed59639
log_event.cc 262 KB