Debian Codegraph @

mysql-test/suite/rpl/t/rpl_special_charset.test

raw
1 ################################################################################
2 # Bug#19855907 IO THREAD AUTHENTICATION ISSUE WITH SOME CHARACTER SETS
3 # Problem: IO thread fails to connect to master if servers are configured with
4 # special character sets like utf16, utf32, ucs2.
5 #
6 # Analysis: MySQL server does not support few special character sets like
7 # utf16,utf32 and ucs2 as "client's character set"(eg: utf16,utf32, ucs2).
8 # When IO thread is trying to connect to Master, it sets server's character
9 # set as client's character set. When Slave server is started with these
10 # special character sets, IO thread (a connection to Master) fails because
11 # of the above said reason.
12 #
13 # Fix: If server's character set is not supported as client's character set,
14 # then set default's client character set(latin1) as client's character set.
15 ###############################################################################
16 --source include/not_group_replication_plugin.inc
17 --source include/master-slave.inc
18 CREATE TABLE t1(i VARCHAR(20)) CHARACTER SET latin1;
19 INSERT INTO t1 VALUES (0xFFFF);
20 --sync_slave_with_master
21 --let diff_tables=master:t1, slave:t1
22 --source include/diff_tables.inc
23 # Cleanup
24 --connection master
25 DROP TABLE t1;
26 --source include/rpl_end.inc