BUG#14157: utf8 encoding in binlog without set character_set_client
refining the test case to exclude problems with koi8r on some platforms.
This commit is contained in:
parent
6d285f8a29
commit
6119b7136e
@ -115,10 +115,10 @@ select HEX(f) from t04;
|
||||
select HEX(f) from t4;
|
||||
|
||||
#
|
||||
#14157: utf8 encoding in binlog without set character_set_client
|
||||
#BUG#14157: utf8 encoding in binlog without set character_set_client
|
||||
#
|
||||
flush logs;
|
||||
--exec $MYSQL test -e 'create table if not exists t5 (a int); set names koi8r; create temporary table `äöüÄÖÜ` (a int); insert into `äöüÄÖÜ` values (1); insert into t5 select * from `äöüÄÖÜ`'
|
||||
--exec $MYSQL test -e 'create table if not exists t5 (a int); set names latin1; create temporary table `äöüÄÖÜ` (a int); insert into `äöüÄÖÜ` values (1); insert into t5 select * from `äöüÄÖÜ`'
|
||||
|
||||
# resulted binlog, parly consisting of multi-byte utf8 chars,
|
||||
# must be digestable for both client and server. In 4.1 the client
|
||||
|
Loading…
x
Reference in New Issue
Block a user