Commit 85528e63 authored by unknown's avatar unknown
Browse files

#14157: utf8 encoding in binlog without set character_set_client 

fixing an issue with the test portability.


mysql-test/t/mysqlbinlog.test:
  BUG#14157: utf8 encoding in binlog without set character_set_client
  
  fixing koi8r specific case to run on all platforms. client does not announce in cmd line any specific
  encoding but rather set it via `set names'.
parent 891361be

mysql-test/t/mysqlbinlog.test

+5 −3
Original line number Diff line number Diff line
@@ -118,10 +118,12 @@ select HEX(f) from t4; 
#14157: utf8 encoding in binlog without set character_set_client

#

flush logs;

--exec $MYSQL --character-sets-dir=../sql/share/charsets/ --default-character-set=koi8r 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 koi8r; create temporary table `` (a int); insert into `` values (1); insert into t5 select * from ``'



# resulted log is client charset insensitive (latin1 not koi8r) as it must be

--exec $MYSQL_BINLOG --short-form $MYSQL_TEST_DIR/var/log/master-bin.000006 | $MYSQL --default-character-set=latin1

# resulted binlog, parly consisting of multi-byte utf8 chars, 

# must be digestable for both client and server. In 4.1 the client 

# should use default-character-set same as the server.

--exec $MYSQL_BINLOG --short-form $MYSQL_TEST_DIR/var/log/master-bin.000006 | $MYSQL

select * from t5  /* must be (1),(1) */;



# clean up