List:Commits« Previous MessageNext Message »
From:Andrei Elkin Date:May 28 2006 4:47pm
Subject:bk commit into 4.1 tree (aelkin:1.2488) BUG#14157
View as plain text  
Below is the list of changes that have just been committed into a local
4.1 repository of elkin. When elkin does a push these changes will
be propagated to the main repository and, within 24 hours after the
push, to the public repository.
For information on how to access the public repository
see http://dev.mysql.com/doc/mysql/en/installing-source-tree.html

ChangeSet
  1.2488 06/05/28 19:47:01 aelkin@stripped +1 -0
  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
    1.21 06/05/28 19:46:57 aelkin@stripped +2 -2
    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.

# This is a BitKeeper patch.  What follows are the unified diffs for the
# set of deltas contained in the patch.  The rest of the patch, the part
# that BitKeeper cares about, is below these diffs.
# User:	aelkin
# Host:	dsl-hkigw8-feb0de00-199.dhcp.inet.fi
# Root:	/usr_rh9/home/elkin.rh9/MySQL/FIXES/4.1-bug14157-utf8_binlog_testcases

--- 1.20/mysql-test/t/mysqlbinlog.test	2006-05-20 12:34:52 +03:00
+++ 1.21/mysql-test/t/mysqlbinlog.test	2006-05-28 19:46:57 +03:00
@@ -115,10 +115,10 @@
 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;
 
 # resulted binlog, parly consisting of multi-byte utf8 chars, 
 # must be digestable for both client and server. In 4.1 the client 
Thread
bk commit into 4.1 tree (aelkin:1.2488) BUG#14157Andrei Elkin28 May