mariadb/rpl_special_charset.result at ef82fd8ca33f0ecab06ddfa11b51dd5ea9019653 - mariadb - GitFox

database/mariadb

mirror of https://github.com/MariaDB/server.git synced 2025-08-31 22:22:30 +03:00

Files

Venkatesh Duggirala ebb2a3f5e1 Problem: IO thread fails to connect to master if servers are configured with

special character sets like utf16, utf32, ucs2.

Analysis: MySQL server does not support few special character sets like
  utf16,utf32 and ucs2 as "client's character set"(eg: utf16,utf32, ucs2).
  It is known limitation listed in the documentation
  http://dev.mysql.com/doc/refman/5.5/en/charset-connection.html.

  The default value for default-character-set parameter is 'auto'
  which means that if the server's character set is not supported,
  then server automatically changes client's character set to
  predefined character-set which is 'latin1' in the current code.

  Eg:
  $ ./mysql -uroot -S$SOCKET_FILE --default-character-set=utf16
  ERROR 1231 (42000): Variable 'character_set_client' can't be set to the value of 'utf16'

  $ ./mysql -uroot -S$SOCKET_FILE will be successfully connected to
  server with 'latin1' as default client side character set.

  When IO thread is trying to connect to Master, it sets server's character
  set as client's character set. When Slave server is started with these
  special character sets, IO thread (which is like a connection to Master)
  fails because of the above said limitation.

 Fix: Now even IO thread also behaves the same as a regular client behaves.
  i.e., If server's character set is not supported as client's character set,
  then set default's client character set(latin1) as client's character set.

2015-01-14 14:13:52 +05:30

8 lines

190 B

Plaintext

Raw Blame History

 include/master-slave.inc
 [connection master]
 CREATE TABLE t1(i VARCHAR(20));
 INSERT INTO t1 VALUES (0xFFFF);
 include/diff_tables.inc [master:t1, slave:t1]
 DROP TABLE t1;
 include/rpl_end.inc