mariadb/mysql-test/suite
sven@riska.(none) 30cd549e3b BUG#34141: mysqlbinlog cannot read 4.1 binlogs containing load data infile
Main problem: mysql 5.1 cannot read binlogs from 4.1.
Subproblem 1: There is a mistake in sql_ex_info::init. The read_str()
function updates its first argument to point to the next character to
read. However, it is applied only to a copy of the buffer pointer, so the
real buffer pointer is not updated.
Fix 1: do not take a copy of the buffer pointer. The copy was needed
because sql_ex_info::init does not use the const attribute on some of its
arguments. So we add the const attribute, too.
Subproblem 2: The first BINLOG statement is asserted to be a
FORMAT_DESCRIPTION_LOG_EVENT, but 4.1 binlogs begin with START_EVENT_V3.
Fix 2: allow START_EVENT_V3 too.
2008-01-30 14:12:40 +01:00
..
binlog BUG#34141: mysqlbinlog cannot read 4.1 binlogs containing load data infile 2008-01-30 14:12:40 +01:00
bugs BUG#31582 (5.1-telco-6.1 -> 5.1.22. Slave crashes when reading UPDATE for VARCHAR): 2007-12-05 20:49:50 +01:00
funcs_1 Merge five.local.lan:/work/merge/mysql-5.0-build-30418 2007-11-21 15:06:38 +01:00
funcs_2 Merge four.local.lan:/WORK2/merge/mysql-5.0-31556 2007-10-18 13:13:21 +02:00
im
jp
large_tests
manual manual merge for bug_29136, bug#29309. 2007-10-13 23:12:50 +03:00
ndb BUG#26395: if crash during autocommit update to transactional table on master, slave fails 2007-12-14 14:40:45 +01:00
ndb_team moving these tests to suite ndb_team 2007-09-05 19:13:36 +02:00
parts Fixes for the bugs 2007-11-20 16:04:07 +01:00
rpl Merge mail.hezx.com:/media/sda3/work/mysql/bkwork/versional/mysql-5.1-new-rpl 2008-01-14 17:59:08 +08:00
rpl_ndb fixed broken result file 2007-12-21 12:22:09 +01:00
stress