From d50e3433b48d224abd7d32d1cf2509624ef40709 Mon Sep 17 00:00:00 2001 From: unknown Date: Sun, 28 May 2006 19:47:01 +0300 Subject: [PATCH] BUG#14157: utf8 encoding in binlog without set character_set_client refining the test case to exclude problems with koi8r on some platforms. mysql-test/t/mysqlbinlog.test: replacing unavailble on some platforms koi8r with latin1 still to preserve the essence of the testcase: to generate utf8 names in binlog, despite client charset was different, and to digest this binlog. --- mysql-test/t/mysqlbinlog.test | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/mysql-test/t/mysqlbinlog.test b/mysql-test/t/mysqlbinlog.test index bf966c2ef64..0e4d16efb64 100644 --- a/mysql-test/t/mysqlbinlog.test +++ b/mysql-test/t/mysqlbinlog.test @@ -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