Commit bac6c908 authored by aelkin@dl145h.mysql.com's avatar aelkin@dl145h.mysql.com

Merge aelkin@bk-internal.mysql.com:/home/bk/mysql-5.1-new

into  dl145h.mysql.com:/tmp/andrei/MERGE/5.1
parents a9ca1339 930325b4
...@@ -190,4 +190,8 @@ select HEX(f) from t4; ...@@ -190,4 +190,8 @@ select HEX(f) from t4;
HEX(f) HEX(f)
835C 835C
flush logs; flush logs;
drop table t1, t2, t03, t04, t3, t4; select * from t5 /* must be (1),(1) */;
a
1
1
drop table t1, t2, t03, t04, t3, t4, t5;
...@@ -125,21 +125,18 @@ select HEX(f) from t04; ...@@ -125,21 +125,18 @@ select HEX(f) from t04;
select HEX(f) from t4; select HEX(f) from t4;
# #
# BUG#14157: utf8 encoding in binlog without set character_set_client #BUG#14157: utf8 encoding in binlog without set character_set_client
#
# BUG:
# This test only works on the MySQL-internal rpl machines.
# Needs to be fixed. Problem is that koi8r is not installed
# on many machines.
# #
flush logs; 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 latin1; 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 # resulted binlog, parly consisting of multi-byte utf8 chars,
# --exec $MYSQL_BINLOG --short-form $MYSQL_TEST_DIR/var/log/master-bin.000006 | $MYSQL --default-character-set=latin1 # must be digestable for both client and server. In 4.1 the client
#select * from t5 /* must be (1),(1) */; # should use default-character-set same as the server.
--exec $MYSQL_BINLOG --short-form $MYSQLTEST_VARDIR/log/master-bin.000006 | $MYSQL
select * from t5 /* must be (1),(1) */;
# clean up # clean up
drop table t1, t2, t03, t04, t3, t4; drop table t1, t2, t03, t04, t3, t4, t5;
# End of 5.0 tests # End of 5.0 tests
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment