2003-09-24 21:25:58 +02:00
|
|
|
|
# We are using .opt file since we need small binlog size
|
2005-12-22 06:39:02 +01:00
|
|
|
|
# TODO: Need to look at making a row based version once the new row based client is completed. [jbm]
|
2006-08-30 09:22:43 +02:00
|
|
|
|
-- source include/have_binlog_format_mixed_or_statement.inc
|
2003-09-24 21:25:58 +02:00
|
|
|
|
|
2007-06-07 19:18:01 +02:00
|
|
|
|
-- source include/have_log_bin.inc
|
2005-03-30 03:17:46 +02:00
|
|
|
|
|
2008-01-08 21:45:15 +01:00
|
|
|
|
# Deletes all the binary logs
|
|
|
|
|
reset master;
|
|
|
|
|
|
2003-09-24 21:25:58 +02:00
|
|
|
|
# we need this for getting fixed timestamps inside of this test
|
|
|
|
|
set timestamp=1000000000;
|
|
|
|
|
|
2004-06-09 16:07:01 +02:00
|
|
|
|
--disable_warnings
|
2007-01-22 14:52:15 +01:00
|
|
|
|
drop table if exists t1,t2,t3,t4,t5,t03,t04;
|
2004-06-09 16:07:01 +02:00
|
|
|
|
--enable_warnings
|
|
|
|
|
|
2003-09-24 21:25:58 +02:00
|
|
|
|
create table t1 (word varchar(20));
|
|
|
|
|
create table t2 (id int auto_increment not null primary key);
|
|
|
|
|
|
|
|
|
|
# simple test for simple statement and various events
|
|
|
|
|
insert into t1 values ("abirvalg");
|
|
|
|
|
insert into t2 values ();
|
|
|
|
|
# Should be uncommented in 4.1
|
|
|
|
|
# set @a:=1
|
|
|
|
|
# insert into t2 values (@a);
|
|
|
|
|
|
2009-03-03 21:34:18 +01:00
|
|
|
|
# test for load data and load data distributed among the several
|
2003-09-24 21:25:58 +02:00
|
|
|
|
# files (we need to fill up first binlog)
|
2007-12-12 18:19:24 +01:00
|
|
|
|
load data infile '../../std_data/words.dat' into table t1;
|
|
|
|
|
load data infile '../../std_data/words.dat' into table t1;
|
|
|
|
|
load data infile '../../std_data/words.dat' into table t1;
|
|
|
|
|
load data infile '../../std_data/words.dat' into table t1;
|
|
|
|
|
load data infile '../../std_data/words.dat' into table t1;
|
2003-09-24 21:25:58 +02:00
|
|
|
|
# simple query to show more in second binlog
|
|
|
|
|
insert into t1 values ("Alas");
|
|
|
|
|
flush logs;
|
|
|
|
|
|
|
|
|
|
# delimiters are for easier debugging in future
|
|
|
|
|
--disable_query_log
|
|
|
|
|
select "--- Local --" as "";
|
|
|
|
|
--enable_query_log
|
|
|
|
|
|
|
|
|
|
#
|
|
|
|
|
# We should use --short-form everywhere because in other case output will
|
|
|
|
|
# be time dependend. Better than nothing.
|
|
|
|
|
#
|
2007-12-12 18:19:24 +01:00
|
|
|
|
let $MYSQLD_DATADIR= `select @@datadir`;
|
2006-01-24 08:30:54 +01:00
|
|
|
|
--replace_result $MYSQLTEST_VARDIR MYSQLTEST_VARDIR
|
2008-02-01 15:34:34 +01:00
|
|
|
|
--replace_regex /SQL_LOAD_MB-[0-9]-[0-9]/SQL_LOAD_MB-#-#/
|
2007-12-12 18:19:24 +01:00
|
|
|
|
--exec $MYSQL_BINLOG --short-form --local-load=$MYSQLTEST_VARDIR/tmp/ $MYSQLD_DATADIR/master-bin.000001
|
2003-09-29 21:10:30 +02:00
|
|
|
|
|
2003-09-24 21:25:58 +02:00
|
|
|
|
# this should not fail but shouldn't produce any working statements
|
|
|
|
|
--disable_query_log
|
|
|
|
|
select "--- Broken LOAD DATA --" as "";
|
|
|
|
|
--enable_query_log
|
2006-01-24 08:30:54 +01:00
|
|
|
|
--replace_result $MYSQLTEST_VARDIR MYSQLTEST_VARDIR
|
2008-02-01 17:26:28 +01:00
|
|
|
|
--replace_regex /SQL_LOAD_MB-[0-9]-[0-9]/SQL_LOAD_MB-#-#/
|
2007-12-12 18:19:24 +01:00
|
|
|
|
--exec $MYSQL_BINLOG --short-form --local-load=$MYSQLTEST_VARDIR/tmp/ $MYSQLD_DATADIR/master-bin.000002 2> /dev/null
|
2003-09-24 21:25:58 +02:00
|
|
|
|
|
|
|
|
|
# this should show almost nothing
|
|
|
|
|
--disable_query_log
|
|
|
|
|
select "--- --database --" as "";
|
|
|
|
|
--enable_query_log
|
2006-01-24 08:30:54 +01:00
|
|
|
|
--replace_result $MYSQLTEST_VARDIR MYSQLTEST_VARDIR
|
2008-02-01 17:26:28 +01:00
|
|
|
|
--replace_regex /SQL_LOAD_MB-[0-9]-[0-9]/SQL_LOAD_MB-#-#/
|
2007-12-12 18:19:24 +01:00
|
|
|
|
--exec $MYSQL_BINLOG --short-form --local-load=$MYSQLTEST_VARDIR/tmp/ --database=nottest $MYSQLD_DATADIR/master-bin.000001 2> /dev/null
|
2003-09-24 21:25:58 +02:00
|
|
|
|
|
|
|
|
|
# this test for position option
|
|
|
|
|
--disable_query_log
|
|
|
|
|
select "--- --position --" as "";
|
|
|
|
|
--enable_query_log
|
2006-01-24 08:30:54 +01:00
|
|
|
|
--replace_result $MYSQLTEST_VARDIR MYSQLTEST_VARDIR
|
2008-02-01 17:26:28 +01:00
|
|
|
|
--replace_regex /SQL_LOAD_MB-[0-9]-[0-9]/SQL_LOAD_MB-#-#/
|
Bug#43746: YACC return wrong query string when parse 'load data infile' sql statement
"load data" statements were written to the binlog as a mix of the original statement
and bits recreated from parse-info. This relied on implementation details and broke
with IGNORE_SPACES and versioned comments.
We now completely resynthesize the query for LOAD DATA for binlog (which among other
things normalizes them somewhat with regard to case, spaces, etc.).
We have already parsed the query properly, so we make use of that rather
than mix-and-match string literals and parsed items.
This should make us safe with regard to versioned comments, even those
spanning multiple tokens. Also no longer affected by IGNORE_SPACES.
mysql-test/r/mysqlbinlog.result:
LOAD DATA INFILE normalized
mysql-test/suite/binlog/r/binlog_killed_simulate.result:
LOAD DATA INFILE normalized
mysql-test/suite/binlog/r/binlog_row_mix_innodb_myisam.result:
LOAD DATA INFILE normalized
mysql-test/suite/binlog/r/binlog_stm_blackhole.result:
LOAD DATA INFILE normalized
mysql-test/suite/binlog/r/binlog_stm_mix_innodb_myisam.result:
LOAD DATA INFILE normalized
mysql-test/suite/rpl/r/rpl_innodb_mixed_dml.result:
LOAD DATA INFILE normalized
mysql-test/suite/rpl/r/rpl_loaddata.result:
LOAD DATA INFILE normalized
mysql-test/suite/rpl/r/rpl_loaddata_fatal.result:
LOAD DATA INFILE normalized; offsets adjusted to reflect that
mysql-test/suite/rpl/r/rpl_loaddata_map.result:
LOAD DATA INFILE normalized
mysql-test/suite/rpl/r/rpl_loaddatalocal.result:
test for #43746 - trying to break LOAD DATA part of parser
mysql-test/suite/rpl/r/rpl_stm_log.result:
LOAD DATA INFILE normalized
mysql-test/suite/rpl/t/rpl_loaddatalocal.test:
try to break the LOAD DATA part of the parser (test for #43746)
mysql-test/t/mysqlbinlog.test:
LOAD DATA INFILE normalized; adjust offsets to reflect that
sql/log_event.cc:
clean up Load_log_event::print_query and friends so they don't print
excess spaces. add support for printing charset names to print_query.
sql/log_event.h:
We already have three places where we synthesize LOAD DATA queries.
Better use one of those!
sql/sql_lex.h:
When binlogging LOAD DATA statements, we make up the statement to
be logged (from the parse-info, rather than substrings of the
original query) now. Consequently, we no longer need (string-)
pointers into the original query.
sql/sql_load.cc:
Completely rewrote write_execute_load_query_log_event() to synthesize the
LOAD DATA statement wholesale, rather than piece it together from
synthesized bits and literal excerpts from the original query. This
will not only give us a nice, normalized statement (all uppercase,
no excess spaces, etc.), it will also handle comments, including
versioned comments right, which is certainly more than we can say
about the previous incarnation.
sql/sql_yacc.yy:
We're no longer assembling LOAD DATA statements from bodyparts of the
original query, so some bookkeeping in the parser can go.
2009-09-28 14:41:10 +02:00
|
|
|
|
--exec $MYSQL_BINLOG --short-form --local-load=$MYSQLTEST_VARDIR/tmp/ --position=330 $MYSQLD_DATADIR/master-bin.000002
|
|
|
|
|
|
2003-09-24 21:25:58 +02:00
|
|
|
|
|
|
|
|
|
# These are tests for remote binlog.
|
|
|
|
|
# They should return the same as previous test.
|
|
|
|
|
|
|
|
|
|
--disable_query_log
|
|
|
|
|
select "--- Remote --" as "";
|
|
|
|
|
--enable_query_log
|
|
|
|
|
|
|
|
|
|
# This is broken now
|
2006-01-24 08:30:54 +01:00
|
|
|
|
--replace_result $MYSQLTEST_VARDIR MYSQLTEST_VARDIR
|
2008-02-01 17:26:28 +01:00
|
|
|
|
--replace_regex /SQL_LOAD_MB-[0-9]-[0-9]/SQL_LOAD_MB-#-#/
|
2006-01-24 08:30:54 +01:00
|
|
|
|
--exec $MYSQL_BINLOG --short-form --local-load=$MYSQLTEST_VARDIR/tmp/ --read-from-remote-server --user=root --host=127.0.0.1 --port=$MASTER_MYPORT master-bin.000001
|
2003-09-24 21:25:58 +02:00
|
|
|
|
|
|
|
|
|
# This is broken too
|
|
|
|
|
--disable_query_log
|
|
|
|
|
select "--- Broken LOAD DATA --" as "";
|
|
|
|
|
--enable_query_log
|
2006-01-24 08:30:54 +01:00
|
|
|
|
--replace_result $MYSQLTEST_VARDIR MYSQLTEST_VARDIR
|
2008-02-01 17:26:28 +01:00
|
|
|
|
--replace_regex /SQL_LOAD_MB-[0-9]-[0-9]/SQL_LOAD_MB-#-#/
|
2006-07-29 11:43:34 +02:00
|
|
|
|
--exec $MYSQL_BINLOG --short-form --local-load=$MYSQLTEST_VARDIR/tmp/ --read-from-remote-server --user=root --host=127.0.0.1 --port=$MASTER_MYPORT master-bin.000002 2> /dev/null
|
2003-09-24 21:25:58 +02:00
|
|
|
|
|
|
|
|
|
# And this too ! (altough it is documented)
|
|
|
|
|
--disable_query_log
|
|
|
|
|
select "--- --database --" as "";
|
|
|
|
|
--enable_query_log
|
2006-01-24 08:30:54 +01:00
|
|
|
|
--replace_result $MYSQLTEST_VARDIR MYSQLTEST_VARDIR
|
2008-02-01 17:26:28 +01:00
|
|
|
|
--replace_regex /SQL_LOAD_MB-[0-9]-[0-9]/SQL_LOAD_MB-#-#/
|
2006-07-29 11:43:34 +02:00
|
|
|
|
--exec $MYSQL_BINLOG --short-form --local-load=$MYSQLTEST_VARDIR/tmp/ --read-from-remote-server --user=root --host=127.0.0.1 --port=$MASTER_MYPORT --database=nottest master-bin.000001 2> /dev/null
|
2003-09-24 21:25:58 +02:00
|
|
|
|
|
|
|
|
|
# Strangely but this works
|
|
|
|
|
--disable_query_log
|
|
|
|
|
select "--- --position --" as "";
|
|
|
|
|
--enable_query_log
|
2006-01-24 08:30:54 +01:00
|
|
|
|
--replace_result $MYSQLTEST_VARDIR MYSQLTEST_VARDIR
|
2008-02-01 17:26:28 +01:00
|
|
|
|
--replace_regex /SQL_LOAD_MB-[0-9]-[0-9]/SQL_LOAD_MB-#-#/
|
Bug#43746: YACC return wrong query string when parse 'load data infile' sql statement
"load data" statements were written to the binlog as a mix of the original statement
and bits recreated from parse-info. This relied on implementation details and broke
with IGNORE_SPACES and versioned comments.
We now completely resynthesize the query for LOAD DATA for binlog (which among other
things normalizes them somewhat with regard to case, spaces, etc.).
We have already parsed the query properly, so we make use of that rather
than mix-and-match string literals and parsed items.
This should make us safe with regard to versioned comments, even those
spanning multiple tokens. Also no longer affected by IGNORE_SPACES.
mysql-test/r/mysqlbinlog.result:
LOAD DATA INFILE normalized
mysql-test/suite/binlog/r/binlog_killed_simulate.result:
LOAD DATA INFILE normalized
mysql-test/suite/binlog/r/binlog_row_mix_innodb_myisam.result:
LOAD DATA INFILE normalized
mysql-test/suite/binlog/r/binlog_stm_blackhole.result:
LOAD DATA INFILE normalized
mysql-test/suite/binlog/r/binlog_stm_mix_innodb_myisam.result:
LOAD DATA INFILE normalized
mysql-test/suite/rpl/r/rpl_innodb_mixed_dml.result:
LOAD DATA INFILE normalized
mysql-test/suite/rpl/r/rpl_loaddata.result:
LOAD DATA INFILE normalized
mysql-test/suite/rpl/r/rpl_loaddata_fatal.result:
LOAD DATA INFILE normalized; offsets adjusted to reflect that
mysql-test/suite/rpl/r/rpl_loaddata_map.result:
LOAD DATA INFILE normalized
mysql-test/suite/rpl/r/rpl_loaddatalocal.result:
test for #43746 - trying to break LOAD DATA part of parser
mysql-test/suite/rpl/r/rpl_stm_log.result:
LOAD DATA INFILE normalized
mysql-test/suite/rpl/t/rpl_loaddatalocal.test:
try to break the LOAD DATA part of the parser (test for #43746)
mysql-test/t/mysqlbinlog.test:
LOAD DATA INFILE normalized; adjust offsets to reflect that
sql/log_event.cc:
clean up Load_log_event::print_query and friends so they don't print
excess spaces. add support for printing charset names to print_query.
sql/log_event.h:
We already have three places where we synthesize LOAD DATA queries.
Better use one of those!
sql/sql_lex.h:
When binlogging LOAD DATA statements, we make up the statement to
be logged (from the parse-info, rather than substrings of the
original query) now. Consequently, we no longer need (string-)
pointers into the original query.
sql/sql_load.cc:
Completely rewrote write_execute_load_query_log_event() to synthesize the
LOAD DATA statement wholesale, rather than piece it together from
synthesized bits and literal excerpts from the original query. This
will not only give us a nice, normalized statement (all uppercase,
no excess spaces, etc.), it will also handle comments, including
versioned comments right, which is certainly more than we can say
about the previous incarnation.
sql/sql_yacc.yy:
We're no longer assembling LOAD DATA statements from bodyparts of the
original query, so some bookkeeping in the parser can go.
2009-09-28 14:41:10 +02:00
|
|
|
|
--exec $MYSQL_BINLOG --short-form --local-load=$MYSQLTEST_VARDIR/tmp/ --read-from-remote-server --position=330 --user=root --host=127.0.0.1 --port=$MASTER_MYPORT master-bin.000002
|
2003-09-24 21:25:58 +02:00
|
|
|
|
|
2009-03-03 21:34:18 +01:00
|
|
|
|
# Bug#7853 mysqlbinlog does not accept input from stdin
|
2005-02-04 14:29:54 +01:00
|
|
|
|
--disable_query_log
|
|
|
|
|
select "--- reading stdin --" as "";
|
|
|
|
|
--enable_query_log
|
|
|
|
|
--replace_result $MYSQL_TEST_DIR MYSQL_TEST_DIR
|
2008-02-01 17:26:28 +01:00
|
|
|
|
--replace_regex /SQL_LOAD_MB-[0-9]-[0-9]/SQL_LOAD_MB-#-#/
|
2005-09-24 04:11:51 +02:00
|
|
|
|
--exec $MYSQL_BINLOG --short-form - < $MYSQL_TEST_DIR/std_data/trunc_binlog.000001
|
2005-02-04 14:29:54 +01:00
|
|
|
|
|
|
|
|
|
--replace_result $MYSQL_TEST_DIR MYSQL_TEST_DIR
|
2008-02-01 17:26:28 +01:00
|
|
|
|
--replace_regex /SQL_LOAD_MB-[0-9]-[0-9]/SQL_LOAD_MB-#-#/
|
2005-09-24 04:11:51 +02:00
|
|
|
|
--exec $MYSQL_BINLOG --short-form --position=79 - < $MYSQL_TEST_DIR/std_data/trunc_binlog.000001
|
2007-01-22 14:52:15 +01:00
|
|
|
|
drop table t1,t2;
|
2005-02-04 14:29:54 +01:00
|
|
|
|
|
2006-05-09 22:01:31 +02:00
|
|
|
|
#
|
2009-03-03 21:34:18 +01:00
|
|
|
|
# Bug#14157 utf8 encoding in binlog without set character_set_client
|
2006-05-09 22:01:31 +02:00
|
|
|
|
#
|
|
|
|
|
flush logs;
|
2007-02-19 17:40:34 +01:00
|
|
|
|
--write_file $MYSQLTEST_VARDIR/tmp/bug14157.sql
|
|
|
|
|
create table if not exists t5 (a int);
|
|
|
|
|
set names latin1;
|
|
|
|
|
create temporary table `<60><><EFBFBD><EFBFBD><EFBFBD><EFBFBD>` (a int);
|
|
|
|
|
insert into `<60><><EFBFBD><EFBFBD><EFBFBD><EFBFBD>` values (1);
|
|
|
|
|
insert into t5 select * from `<60><><EFBFBD><EFBFBD><EFBFBD><EFBFBD>`
|
|
|
|
|
EOF
|
|
|
|
|
--exec $MYSQL test < $MYSQLTEST_VARDIR/tmp/bug14157.sql
|
|
|
|
|
--remove_file $MYSQLTEST_VARDIR/tmp/bug14157.sql
|
2006-02-09 15:23:09 +01:00
|
|
|
|
|
2009-03-03 21:34:18 +01:00
|
|
|
|
# resulted binlog, parly consisting of multi-byte utf8 chars,
|
|
|
|
|
# must be digestable for both client and server. In 4.1 the client
|
2006-05-20 11:34:56 +02:00
|
|
|
|
# should use default-character-set same as the server.
|
2006-12-14 11:05:25 +01:00
|
|
|
|
flush logs;
|
2007-12-12 18:19:24 +01:00
|
|
|
|
--exec $MYSQL_BINLOG --short-form $MYSQLD_DATADIR/master-bin.000004 | $MYSQL
|
2006-05-09 22:01:31 +02:00
|
|
|
|
select * from t5 /* must be (1),(1) */;
|
2007-01-22 14:52:15 +01:00
|
|
|
|
drop table t5;
|
2006-02-09 15:23:09 +01:00
|
|
|
|
|
2006-12-07 06:31:53 +01:00
|
|
|
|
#
|
|
|
|
|
# Bug#22645 LC_TIME_NAMES: Statement not replicated
|
|
|
|
|
# Check that a dump created by mysqlbinlog reproduces
|
|
|
|
|
# lc_time_names dependent values correctly
|
|
|
|
|
#
|
|
|
|
|
flush logs;
|
|
|
|
|
create table t5 (c1 int, c2 varchar(128) character set latin1 not null);
|
|
|
|
|
insert into t5 values (1, date_format('2001-01-01','%W'));
|
|
|
|
|
set lc_time_names=de_DE;
|
|
|
|
|
insert into t5 values (2, date_format('2001-01-01','%W'));
|
|
|
|
|
set lc_time_names=en_US;
|
|
|
|
|
insert into t5 values (3, date_format('2001-01-01','%W'));
|
|
|
|
|
select * from t5 order by c1;
|
|
|
|
|
flush logs;
|
|
|
|
|
drop table t5;
|
2007-12-12 18:19:24 +01:00
|
|
|
|
--exec $MYSQL_BINLOG --short-form $MYSQLD_DATADIR/master-bin.000006 | $MYSQL
|
2006-12-07 06:31:53 +01:00
|
|
|
|
select * from t5 order by c1;
|
2007-01-22 14:52:15 +01:00
|
|
|
|
drop table t5;
|
|
|
|
|
|
2006-11-28 13:26:15 +01:00
|
|
|
|
#
|
2009-03-03 21:34:18 +01:00
|
|
|
|
# Bug#20396 Bin Log does not get DELIMETER cmd - Recover StoredProc fails
|
2006-11-28 13:26:15 +01:00
|
|
|
|
#
|
|
|
|
|
--disable_warnings
|
|
|
|
|
drop procedure if exists p1;
|
|
|
|
|
--enable_warnings
|
|
|
|
|
flush logs;
|
|
|
|
|
delimiter //;
|
|
|
|
|
create procedure p1()
|
|
|
|
|
begin
|
|
|
|
|
select 1;
|
|
|
|
|
end;
|
|
|
|
|
//
|
|
|
|
|
delimiter ;//
|
|
|
|
|
flush logs;
|
|
|
|
|
call p1();
|
|
|
|
|
drop procedure p1;
|
2009-02-19 21:37:40 +01:00
|
|
|
|
--error ER_SP_DOES_NOT_EXIST
|
2006-11-28 13:26:15 +01:00
|
|
|
|
call p1();
|
2008-02-01 17:26:28 +01:00
|
|
|
|
--replace_regex /SQL_LOAD_MB-[0-9]-[0-9]/SQL_LOAD_MB-#-#/
|
2007-12-12 18:19:24 +01:00
|
|
|
|
--exec $MYSQL_BINLOG --short-form $MYSQLD_DATADIR/master-bin.000008
|
|
|
|
|
--exec $MYSQL_BINLOG --short-form $MYSQLD_DATADIR/master-bin.000008 | $MYSQL
|
2006-11-28 13:26:15 +01:00
|
|
|
|
call p1();
|
|
|
|
|
drop procedure p1;
|
|
|
|
|
|
2007-01-22 14:52:15 +01:00
|
|
|
|
#
|
2006-12-14 23:51:37 +01:00
|
|
|
|
# Some coverage of not normally used parts
|
|
|
|
|
#
|
|
|
|
|
--disable_query_log
|
|
|
|
|
--exec $MYSQL_BINLOG --version 2>&1 > /dev/null
|
|
|
|
|
--exec $MYSQL_BINLOG --help 2>&1 > /dev/null
|
|
|
|
|
--enable_query_log
|
2005-02-14 21:50:09 +01:00
|
|
|
|
|
2007-02-28 14:06:57 +01:00
|
|
|
|
#
|
|
|
|
|
# Bug#15126 character_set_database is not replicated
|
|
|
|
|
# (LOAD DATA INFILE need it)
|
|
|
|
|
#
|
|
|
|
|
|
|
|
|
|
flush logs;
|
|
|
|
|
create table t1 (a varchar(64) character set utf8);
|
2007-12-12 18:19:24 +01:00
|
|
|
|
load data infile '../../std_data/loaddata6.dat' into table t1;
|
2007-02-28 14:06:57 +01:00
|
|
|
|
set character_set_database=koi8r;
|
2007-12-12 18:19:24 +01:00
|
|
|
|
load data infile '../../std_data/loaddata6.dat' into table t1;
|
2007-02-28 14:06:57 +01:00
|
|
|
|
set character_set_database=latin1;
|
2007-12-12 18:19:24 +01:00
|
|
|
|
load data infile '../../std_data/loaddata6.dat' into table t1;
|
|
|
|
|
load data infile '../../std_data/loaddata6.dat' into table t1;
|
2007-02-28 14:06:57 +01:00
|
|
|
|
set character_set_database=koi8r;
|
2007-12-12 18:19:24 +01:00
|
|
|
|
load data infile '../../std_data/loaddata6.dat' into table t1;
|
2007-02-28 14:06:57 +01:00
|
|
|
|
set character_set_database=latin1;
|
2007-12-12 18:19:24 +01:00
|
|
|
|
load data infile '../../std_data/loaddata6.dat' into table t1;
|
|
|
|
|
load data infile '../../std_data/loaddata6.dat' into table t1 character set koi8r;
|
2007-02-28 14:06:57 +01:00
|
|
|
|
select hex(a) from t1;
|
|
|
|
|
drop table t1;
|
|
|
|
|
flush logs;
|
2007-03-31 17:18:03 +02:00
|
|
|
|
--replace_result $MYSQLTEST_VARDIR MYSQLTEST_VARDIR
|
2008-02-01 17:26:28 +01:00
|
|
|
|
--replace_regex /SQL_LOAD_MB-[0-9]-[0-9]/SQL_LOAD_MB-#-#/
|
2007-12-12 18:19:24 +01:00
|
|
|
|
--exec $MYSQL_BINLOG --short-form --local-load=$MYSQLTEST_VARDIR/tmp/ $MYSQLD_DATADIR/master-bin.000010
|
2006-11-28 13:26:15 +01:00
|
|
|
|
|
2007-06-20 23:11:28 +02:00
|
|
|
|
#
|
|
|
|
|
# Bug#28293 missed '#' sign in the hex dump when the dump length
|
2009-03-05 14:35:03 +01:00
|
|
|
|
# is divisible by 16.
|
2007-06-20 23:11:28 +02:00
|
|
|
|
#
|
|
|
|
|
|
|
|
|
|
CREATE TABLE t1 (c1 CHAR(10));
|
|
|
|
|
# we need this for getting fixed timestamps inside of this test
|
2009-03-03 21:34:18 +01:00
|
|
|
|
FLUSH LOGS;
|
2007-06-20 23:11:28 +02:00
|
|
|
|
INSERT INTO t1 VALUES ('0123456789');
|
2009-03-03 21:34:18 +01:00
|
|
|
|
FLUSH LOGS;
|
2007-06-20 23:11:28 +02:00
|
|
|
|
DROP TABLE t1;
|
2009-02-19 21:37:40 +01:00
|
|
|
|
|
|
|
|
|
# We create a table, patch, and load the output into it
|
|
|
|
|
# By using LINES STARTING BY '#' + SELECT WHERE a LIKE 'Query'
|
|
|
|
|
# We can easily see if a 'Query' line is missing the '#' character
|
|
|
|
|
# as described in the original bug
|
|
|
|
|
|
2009-03-05 14:35:03 +01:00
|
|
|
|
--disable_query_log
|
|
|
|
|
CREATE TABLE patch (a BLOB);
|
2009-02-20 00:24:25 +01:00
|
|
|
|
--exec $MYSQL_BINLOG --hexdump --local-load=$MYSQLTEST_VARDIR/tmp/ $MYSQLD_DATADIR/master-bin.000012 > $MYSQLTEST_VARDIR/tmp/mysqlbinlog_tmp.dat
|
2009-02-19 21:37:40 +01:00
|
|
|
|
eval LOAD DATA LOCAL INFILE '$MYSQLTEST_VARDIR/tmp/mysqlbinlog_tmp.dat'
|
2009-03-05 14:35:03 +01:00
|
|
|
|
INTO TABLE patch FIELDS TERMINATED BY '' LINES STARTING BY '#';
|
2009-02-19 21:37:40 +01:00
|
|
|
|
--remove_file $MYSQLTEST_VARDIR/tmp/mysqlbinlog_tmp.dat
|
|
|
|
|
--enable_query_log
|
|
|
|
|
|
|
|
|
|
--echo We expect this value to be 1
|
|
|
|
|
--echo The bug being tested was that 'Query' lines were not preceded by '#'
|
|
|
|
|
--echo If the line is in the table, it had to have been preceded by a '#'
|
|
|
|
|
--echo
|
|
|
|
|
SELECT COUNT(*) AS `BUG#28293_expect_1` FROM patch WHERE a LIKE '%Query%';
|
|
|
|
|
DROP TABLE patch;
|
2007-06-20 23:11:28 +02:00
|
|
|
|
|
Fix for bug #29928: INSERT ... VALUES(connection_id(), ...) incorrect
restores from mysqlbinlog out
Problem: using "mysqlbinlog | mysql" for recoveries the connection_id()
result may differ from what was used when issuing the statement.
Fix: if there is a connection_id() in a statement, write to binlog
SET pseudo_thread_id= XXX; before it and use the value later on.
mysql-test/r/mysqlbinlog.result:
Fix for bug #29928: INSERT ... VALUES(connection_id(), ...) incorrect
restores from mysqlbinlog out
- test result.
mysql-test/t/mysqlbinlog.test:
Fix for bug #29928: INSERT ... VALUES(connection_id(), ...) incorrect
restores from mysqlbinlog out
- test case.
sql/item_create.cc:
Fix for bug #29928: INSERT ... VALUES(connection_id(), ...) incorrect
restores from mysqlbinlog out
- set thread_specific_used flag for the connection_id() function.
sql/item_func.cc:
Fix for bug #29928: INSERT ... VALUES(connection_id(), ...) incorrect
restores from mysqlbinlog out
- always return thd->variables.pseudo_thread_id as a connection_id()
result, as it contains a proper value for both master and slave.
sql/log_event.cc:
Fix for bug #29928: INSERT ... VALUES(connection_id(), ...) incorrect
restores from mysqlbinlog out
- set LOG_EVENT_THREAD_SPECIFIC_F event flag if thread_specific_used
is set.
sql/sql_class.cc:
Fix for bug #29928: INSERT ... VALUES(connection_id(), ...) incorrect
restores from mysqlbinlog out
- thd->thread_specific_used introduced, which is set if thread specific
value(s) used in a statement.
sql/sql_class.h:
Fix for bug #29928: INSERT ... VALUES(connection_id(), ...) incorrect
restores from mysqlbinlog out
- thd->thread_specific_used introduced, which is set if thread specific
value(s) used in a statement.
2007-08-01 12:27:03 +02:00
|
|
|
|
#
|
2009-03-03 21:34:18 +01:00
|
|
|
|
# Bug#29928 incorrect connection_id() restoring from mysqlbinlog out
|
Fix for bug #29928: INSERT ... VALUES(connection_id(), ...) incorrect
restores from mysqlbinlog out
Problem: using "mysqlbinlog | mysql" for recoveries the connection_id()
result may differ from what was used when issuing the statement.
Fix: if there is a connection_id() in a statement, write to binlog
SET pseudo_thread_id= XXX; before it and use the value later on.
mysql-test/r/mysqlbinlog.result:
Fix for bug #29928: INSERT ... VALUES(connection_id(), ...) incorrect
restores from mysqlbinlog out
- test result.
mysql-test/t/mysqlbinlog.test:
Fix for bug #29928: INSERT ... VALUES(connection_id(), ...) incorrect
restores from mysqlbinlog out
- test case.
sql/item_create.cc:
Fix for bug #29928: INSERT ... VALUES(connection_id(), ...) incorrect
restores from mysqlbinlog out
- set thread_specific_used flag for the connection_id() function.
sql/item_func.cc:
Fix for bug #29928: INSERT ... VALUES(connection_id(), ...) incorrect
restores from mysqlbinlog out
- always return thd->variables.pseudo_thread_id as a connection_id()
result, as it contains a proper value for both master and slave.
sql/log_event.cc:
Fix for bug #29928: INSERT ... VALUES(connection_id(), ...) incorrect
restores from mysqlbinlog out
- set LOG_EVENT_THREAD_SPECIFIC_F event flag if thread_specific_used
is set.
sql/sql_class.cc:
Fix for bug #29928: INSERT ... VALUES(connection_id(), ...) incorrect
restores from mysqlbinlog out
- thd->thread_specific_used introduced, which is set if thread specific
value(s) used in a statement.
sql/sql_class.h:
Fix for bug #29928: INSERT ... VALUES(connection_id(), ...) incorrect
restores from mysqlbinlog out
- thd->thread_specific_used introduced, which is set if thread specific
value(s) used in a statement.
2007-08-01 12:27:03 +02:00
|
|
|
|
#
|
2009-03-03 21:34:18 +01:00
|
|
|
|
FLUSH LOGS;
|
|
|
|
|
CREATE TABLE t1(a INT);
|
|
|
|
|
INSERT INTO t1 VALUES(connection_id());
|
|
|
|
|
let $a= `SELECT a FROM t1`;
|
|
|
|
|
FLUSH LOGS;
|
2009-03-06 15:56:17 +01:00
|
|
|
|
let $outfile= $MYSQLTEST_VARDIR/tmp/bug29928.sql;
|
|
|
|
|
--exec $MYSQL_BINLOG $MYSQLD_DATADIR/master-bin.000014 > $outfile
|
2009-03-03 21:34:18 +01:00
|
|
|
|
DROP TABLE t1;
|
|
|
|
|
connect (con1, localhost, root, , test);
|
Fix for bug #29928: INSERT ... VALUES(connection_id(), ...) incorrect
restores from mysqlbinlog out
Problem: using "mysqlbinlog | mysql" for recoveries the connection_id()
result may differ from what was used when issuing the statement.
Fix: if there is a connection_id() in a statement, write to binlog
SET pseudo_thread_id= XXX; before it and use the value later on.
mysql-test/r/mysqlbinlog.result:
Fix for bug #29928: INSERT ... VALUES(connection_id(), ...) incorrect
restores from mysqlbinlog out
- test result.
mysql-test/t/mysqlbinlog.test:
Fix for bug #29928: INSERT ... VALUES(connection_id(), ...) incorrect
restores from mysqlbinlog out
- test case.
sql/item_create.cc:
Fix for bug #29928: INSERT ... VALUES(connection_id(), ...) incorrect
restores from mysqlbinlog out
- set thread_specific_used flag for the connection_id() function.
sql/item_func.cc:
Fix for bug #29928: INSERT ... VALUES(connection_id(), ...) incorrect
restores from mysqlbinlog out
- always return thd->variables.pseudo_thread_id as a connection_id()
result, as it contains a proper value for both master and slave.
sql/log_event.cc:
Fix for bug #29928: INSERT ... VALUES(connection_id(), ...) incorrect
restores from mysqlbinlog out
- set LOG_EVENT_THREAD_SPECIFIC_F event flag if thread_specific_used
is set.
sql/sql_class.cc:
Fix for bug #29928: INSERT ... VALUES(connection_id(), ...) incorrect
restores from mysqlbinlog out
- thd->thread_specific_used introduced, which is set if thread specific
value(s) used in a statement.
sql/sql_class.h:
Fix for bug #29928: INSERT ... VALUES(connection_id(), ...) incorrect
restores from mysqlbinlog out
- thd->thread_specific_used introduced, which is set if thread specific
value(s) used in a statement.
2007-08-01 12:27:03 +02:00
|
|
|
|
connection con1;
|
2009-03-06 15:56:17 +01:00
|
|
|
|
--exec $MYSQL test < $outfile
|
|
|
|
|
--remove_file $outfile
|
2009-03-03 21:34:18 +01:00
|
|
|
|
let $b= `SELECT a FROM t1`;
|
Fix for bug #29928: INSERT ... VALUES(connection_id(), ...) incorrect
restores from mysqlbinlog out
Problem: using "mysqlbinlog | mysql" for recoveries the connection_id()
result may differ from what was used when issuing the statement.
Fix: if there is a connection_id() in a statement, write to binlog
SET pseudo_thread_id= XXX; before it and use the value later on.
mysql-test/r/mysqlbinlog.result:
Fix for bug #29928: INSERT ... VALUES(connection_id(), ...) incorrect
restores from mysqlbinlog out
- test result.
mysql-test/t/mysqlbinlog.test:
Fix for bug #29928: INSERT ... VALUES(connection_id(), ...) incorrect
restores from mysqlbinlog out
- test case.
sql/item_create.cc:
Fix for bug #29928: INSERT ... VALUES(connection_id(), ...) incorrect
restores from mysqlbinlog out
- set thread_specific_used flag for the connection_id() function.
sql/item_func.cc:
Fix for bug #29928: INSERT ... VALUES(connection_id(), ...) incorrect
restores from mysqlbinlog out
- always return thd->variables.pseudo_thread_id as a connection_id()
result, as it contains a proper value for both master and slave.
sql/log_event.cc:
Fix for bug #29928: INSERT ... VALUES(connection_id(), ...) incorrect
restores from mysqlbinlog out
- set LOG_EVENT_THREAD_SPECIFIC_F event flag if thread_specific_used
is set.
sql/sql_class.cc:
Fix for bug #29928: INSERT ... VALUES(connection_id(), ...) incorrect
restores from mysqlbinlog out
- thd->thread_specific_used introduced, which is set if thread specific
value(s) used in a statement.
sql/sql_class.h:
Fix for bug #29928: INSERT ... VALUES(connection_id(), ...) incorrect
restores from mysqlbinlog out
- thd->thread_specific_used introduced, which is set if thread specific
value(s) used in a statement.
2007-08-01 12:27:03 +02:00
|
|
|
|
disconnect con1;
|
|
|
|
|
connection default;
|
2009-03-03 21:34:18 +01:00
|
|
|
|
let $c= `SELECT $a=$b`;
|
Fix for bug #29928: INSERT ... VALUES(connection_id(), ...) incorrect
restores from mysqlbinlog out
Problem: using "mysqlbinlog | mysql" for recoveries the connection_id()
result may differ from what was used when issuing the statement.
Fix: if there is a connection_id() in a statement, write to binlog
SET pseudo_thread_id= XXX; before it and use the value later on.
mysql-test/r/mysqlbinlog.result:
Fix for bug #29928: INSERT ... VALUES(connection_id(), ...) incorrect
restores from mysqlbinlog out
- test result.
mysql-test/t/mysqlbinlog.test:
Fix for bug #29928: INSERT ... VALUES(connection_id(), ...) incorrect
restores from mysqlbinlog out
- test case.
sql/item_create.cc:
Fix for bug #29928: INSERT ... VALUES(connection_id(), ...) incorrect
restores from mysqlbinlog out
- set thread_specific_used flag for the connection_id() function.
sql/item_func.cc:
Fix for bug #29928: INSERT ... VALUES(connection_id(), ...) incorrect
restores from mysqlbinlog out
- always return thd->variables.pseudo_thread_id as a connection_id()
result, as it contains a proper value for both master and slave.
sql/log_event.cc:
Fix for bug #29928: INSERT ... VALUES(connection_id(), ...) incorrect
restores from mysqlbinlog out
- set LOG_EVENT_THREAD_SPECIFIC_F event flag if thread_specific_used
is set.
sql/sql_class.cc:
Fix for bug #29928: INSERT ... VALUES(connection_id(), ...) incorrect
restores from mysqlbinlog out
- thd->thread_specific_used introduced, which is set if thread specific
value(s) used in a statement.
sql/sql_class.h:
Fix for bug #29928: INSERT ... VALUES(connection_id(), ...) incorrect
restores from mysqlbinlog out
- thd->thread_specific_used introduced, which is set if thread specific
value(s) used in a statement.
2007-08-01 12:27:03 +02:00
|
|
|
|
--echo $c
|
2009-03-03 21:34:18 +01:00
|
|
|
|
DROP TABLE t1;
|
Fix for bug #29928: INSERT ... VALUES(connection_id(), ...) incorrect
restores from mysqlbinlog out
Problem: using "mysqlbinlog | mysql" for recoveries the connection_id()
result may differ from what was used when issuing the statement.
Fix: if there is a connection_id() in a statement, write to binlog
SET pseudo_thread_id= XXX; before it and use the value later on.
mysql-test/r/mysqlbinlog.result:
Fix for bug #29928: INSERT ... VALUES(connection_id(), ...) incorrect
restores from mysqlbinlog out
- test result.
mysql-test/t/mysqlbinlog.test:
Fix for bug #29928: INSERT ... VALUES(connection_id(), ...) incorrect
restores from mysqlbinlog out
- test case.
sql/item_create.cc:
Fix for bug #29928: INSERT ... VALUES(connection_id(), ...) incorrect
restores from mysqlbinlog out
- set thread_specific_used flag for the connection_id() function.
sql/item_func.cc:
Fix for bug #29928: INSERT ... VALUES(connection_id(), ...) incorrect
restores from mysqlbinlog out
- always return thd->variables.pseudo_thread_id as a connection_id()
result, as it contains a proper value for both master and slave.
sql/log_event.cc:
Fix for bug #29928: INSERT ... VALUES(connection_id(), ...) incorrect
restores from mysqlbinlog out
- set LOG_EVENT_THREAD_SPECIFIC_F event flag if thread_specific_used
is set.
sql/sql_class.cc:
Fix for bug #29928: INSERT ... VALUES(connection_id(), ...) incorrect
restores from mysqlbinlog out
- thd->thread_specific_used introduced, which is set if thread specific
value(s) used in a statement.
sql/sql_class.h:
Fix for bug #29928: INSERT ... VALUES(connection_id(), ...) incorrect
restores from mysqlbinlog out
- thd->thread_specific_used introduced, which is set if thread specific
value(s) used in a statement.
2007-08-01 12:27:03 +02:00
|
|
|
|
|
2007-11-09 13:43:09 +01:00
|
|
|
|
echo shell> mysqlbinlog std_data/corrupt-relay-bin.000624 > var/tmp/bug31793.sql;
|
|
|
|
|
error 1;
|
|
|
|
|
exec $MYSQL_BINLOG $MYSQL_TEST_DIR/std_data/corrupt-relay-bin.000624 > $MYSQLTEST_VARDIR/tmp/bug31793.sql;
|
2009-03-06 15:56:17 +01:00
|
|
|
|
--remove_file $MYSQLTEST_VARDIR/tmp/bug31793.sql
|
2007-11-09 13:43:09 +01:00
|
|
|
|
|
2006-12-14 11:05:25 +01:00
|
|
|
|
|
|
|
|
|
#
|
|
|
|
|
# Test --disable-force-if-open and --force-if-open
|
|
|
|
|
#
|
2009-03-06 15:56:17 +01:00
|
|
|
|
FLUSH LOGS;
|
2006-12-14 11:05:25 +01:00
|
|
|
|
--error 1
|
2007-12-12 18:19:24 +01:00
|
|
|
|
--exec $MYSQL_BINLOG $MYSQLD_DATADIR/master-bin.000016 >/dev/null 2>/dev/null
|
|
|
|
|
--exec $MYSQL_BINLOG --force-if-open $MYSQLD_DATADIR/master-bin.000016 >/dev/null 2>/dev/null
|
2006-12-14 11:05:25 +01:00
|
|
|
|
|
2009-03-06 15:56:17 +01:00
|
|
|
|
--echo Bug#31611 Security risk with BINLOG statement
|
2007-11-03 01:33:48 +01:00
|
|
|
|
|
|
|
|
|
SET BINLOG_FORMAT=ROW;
|
|
|
|
|
CREATE DATABASE mysqltest1;
|
|
|
|
|
CREATE USER untrusted@localhost;
|
|
|
|
|
GRANT SELECT ON mysqltest1.* TO untrusted@localhost;
|
|
|
|
|
|
|
|
|
|
SHOW GRANTS FOR untrusted@localhost;
|
|
|
|
|
USE mysqltest1;
|
|
|
|
|
CREATE TABLE t1 (a INT, b CHAR(64));
|
|
|
|
|
flush logs;
|
|
|
|
|
INSERT INTO t1 VALUES (1,USER());
|
|
|
|
|
flush logs;
|
|
|
|
|
echo mysqlbinlog var/log/master-bin.000017 > var/tmp/bug31611.sql;
|
2007-12-12 18:19:24 +01:00
|
|
|
|
exec $MYSQL_BINLOG $MYSQLD_DATADIR/master-bin.000017 > $MYSQLTEST_VARDIR/tmp/bug31611.sql;
|
2007-11-03 01:33:48 +01:00
|
|
|
|
connect (unsecure,localhost,untrusted,,mysqltest1);
|
|
|
|
|
echo mysql mysqltest1 -uuntrusted < var/tmp/bug31611.sql;
|
|
|
|
|
error 1;
|
|
|
|
|
exec $MYSQL mysqltest1 -uuntrusted < $MYSQLTEST_VARDIR/tmp/bug31611.sql;
|
2009-03-06 15:56:17 +01:00
|
|
|
|
--remove_file $MYSQLTEST_VARDIR/tmp/bug31611.sql
|
2007-11-03 01:33:48 +01:00
|
|
|
|
connection unsecure;
|
|
|
|
|
error ER_TABLEACCESS_DENIED_ERROR;
|
|
|
|
|
INSERT INTO t1 VALUES (1,USER());
|
|
|
|
|
|
|
|
|
|
SELECT * FROM t1;
|
|
|
|
|
connection default;
|
|
|
|
|
DROP DATABASE mysqltest1;
|
2007-11-12 11:29:55 +01:00
|
|
|
|
DROP USER untrusted@localhost;
|
2007-11-03 01:33:48 +01:00
|
|
|
|
|
2009-03-06 15:56:17 +01:00
|
|
|
|
--echo Bug#32580 mysqlbinlog cannot read binlog event with user variables
|
2007-11-23 14:41:41 +01:00
|
|
|
|
|
|
|
|
|
# Testing that various kinds of events can be read and restored properly.
|
|
|
|
|
|
|
|
|
|
connection default;
|
|
|
|
|
USE test;
|
|
|
|
|
SET BINLOG_FORMAT = STATEMENT;
|
|
|
|
|
FLUSH LOGS;
|
|
|
|
|
CREATE TABLE t1 (a_real FLOAT, an_int INT, a_decimal DECIMAL(5,2), a_string CHAR(32));
|
|
|
|
|
SET @a_real = rand(20) * 1000;
|
|
|
|
|
SET @an_int = 1000;
|
|
|
|
|
SET @a_decimal = CAST(rand(19) * 999 AS DECIMAL(5,2));
|
|
|
|
|
SET @a_string = 'Just a test';
|
|
|
|
|
INSERT INTO t1 VALUES (@a_real, @an_int, @a_decimal, @a_string);
|
|
|
|
|
FLUSH LOGS;
|
|
|
|
|
query_vertical SELECT * FROM t1;
|
|
|
|
|
DROP TABLE t1;
|
|
|
|
|
|
|
|
|
|
echo >> mysqlbinlog var/log/master-bin.000019 > var/tmp/bug32580.sql;
|
2007-12-12 18:19:24 +01:00
|
|
|
|
exec $MYSQL_BINLOG $MYSQLD_DATADIR/master-bin.000019 > $MYSQLTEST_VARDIR/tmp/bug32580.sql;
|
2007-11-23 14:41:41 +01:00
|
|
|
|
echo >> mysql test < var/tmp/bug32580.sql;
|
|
|
|
|
exec $MYSQL test < $MYSQLTEST_VARDIR/tmp/bug32580.sql;
|
|
|
|
|
remove_file $MYSQLTEST_VARDIR/tmp/bug32580.sql;
|
|
|
|
|
|
|
|
|
|
query_vertical SELECT * FROM t1;
|
|
|
|
|
DROP TABLE t1;
|
|
|
|
|
|
2009-02-20 12:55:43 +01:00
|
|
|
|
#
|
2009-03-05 14:35:03 +01:00
|
|
|
|
# Bug#37313 BINLOG Contains Incorrect server id
|
2009-02-20 12:55:43 +01:00
|
|
|
|
#
|
|
|
|
|
|
2009-03-05 14:35:03 +01:00
|
|
|
|
let $binlog_file= $MYSQLTEST_VARDIR/tmp/mysqlbinlog_bug37313.binlog;
|
|
|
|
|
let $save_server_id= `SELECT @@global.server_id`;
|
|
|
|
|
let $s_id_max= `SELECT (1 << 32) - 1`;
|
|
|
|
|
eval SET @@global.server_id= $s_id_max;
|
2009-02-20 12:55:43 +01:00
|
|
|
|
|
2009-03-05 14:35:03 +01:00
|
|
|
|
RESET MASTER;
|
|
|
|
|
FLUSH LOGS;
|
2009-03-06 15:56:17 +01:00
|
|
|
|
--exec $MYSQL_BINLOG $MYSQLD_DATADIR/master-bin.000001 > $binlog_file
|
2009-02-20 12:55:43 +01:00
|
|
|
|
--replace_result $MYSQLTEST_VARDIR MYSQLTEST_VARDIR
|
2009-03-05 14:35:03 +01:00
|
|
|
|
eval SELECT
|
|
|
|
|
(@a:=LOAD_FILE("$binlog_file"))
|
|
|
|
|
IS NOT NULL;
|
|
|
|
|
let $s_id_unsigned= `SELECT @a LIKE "%server id $s_id_max%" /* must return 1 */`;
|
2009-02-20 12:55:43 +01:00
|
|
|
|
echo *** Unsigned server_id $s_id_max is found: $s_id_unsigned ***;
|
|
|
|
|
|
2009-03-05 14:35:03 +01:00
|
|
|
|
eval SET @@global.server_id= $save_server_id;
|
|
|
|
|
--remove_file $binlog_file
|
2009-02-20 12:55:43 +01:00
|
|
|
|
|
2009-05-07 16:31:02 +02:00
|
|
|
|
#
|
|
|
|
|
# Bug #41943: mysqlbinlog.exe crashes if --hexdump option is used
|
|
|
|
|
#
|
|
|
|
|
|
|
|
|
|
RESET MASTER;
|
|
|
|
|
FLUSH LOGS;
|
|
|
|
|
|
|
|
|
|
# We do not need the results, just make sure that mysqlbinlog does not crash
|
|
|
|
|
--exec $MYSQL_BINLOG --hexdump --read-from-remote-server --user=root --host=127.0.0.1 --port=$MASTER_MYPORT master-bin.000001 >/dev/null
|
|
|
|
|
|
2009-09-30 04:01:52 +02:00
|
|
|
|
#
|
|
|
|
|
# #46998
|
|
|
|
|
# This test verifies if the 'BEGIN', 'COMMIT' and 'ROLLBACK' are output
|
|
|
|
|
# in regardless of database filtering
|
|
|
|
|
#
|
|
|
|
|
|
|
|
|
|
RESET MASTER;
|
|
|
|
|
FLUSH LOGS;
|
|
|
|
|
|
|
|
|
|
# The following three test cases were wrtten into binlog_transaction.000001
|
|
|
|
|
# Test case1: Test if the 'BEGIN' and 'COMMIT' are output for the 'test' database
|
|
|
|
|
# in transaction1 base on innodb engine tables
|
|
|
|
|
# use test;
|
|
|
|
|
# create table t1(a int) engine= innodb;
|
|
|
|
|
# use mysql;
|
|
|
|
|
# create table t2(a int) engine= innodb;
|
|
|
|
|
# Transaction1 begin
|
|
|
|
|
# begin;
|
|
|
|
|
# use test;
|
|
|
|
|
# insert into t1 (a) values (1);
|
|
|
|
|
# use mysql;
|
|
|
|
|
# insert into t2 (a) values (1);
|
|
|
|
|
# commit;
|
|
|
|
|
# Transaction1 end
|
|
|
|
|
|
|
|
|
|
# Test case2: Test if the 'BEGIN' and 'ROLLBACK' are output for the 'test' database
|
|
|
|
|
# in transaction2 base on innodb and myisam engine tables
|
|
|
|
|
# use test;
|
|
|
|
|
# create table t3(a int) engine= innodb;
|
|
|
|
|
# use mysql;
|
|
|
|
|
# create table t4(a int) engine= myisam;
|
|
|
|
|
# Transaction2 begin
|
|
|
|
|
# begin;
|
|
|
|
|
# use test;
|
|
|
|
|
# insert into t3 (a) values (2);
|
|
|
|
|
# use mysql;
|
|
|
|
|
# insert into t4 (a) values (2);
|
|
|
|
|
# rollback;
|
|
|
|
|
# Transaction2 end
|
|
|
|
|
|
|
|
|
|
# Test case3: Test if the 'BEGIN' and 'COMMIT' are output for the 'test' database
|
|
|
|
|
# in transaction3 base on NDB engine tables
|
|
|
|
|
# use test;
|
|
|
|
|
# create table t5(a int) engine= NDB;
|
|
|
|
|
# use mysql;
|
|
|
|
|
# create table t6(a int) engine= NDB;
|
|
|
|
|
# Transaction3 begin
|
|
|
|
|
# begin;
|
|
|
|
|
# use test;
|
|
|
|
|
# insert into t5 (a) values (3);
|
|
|
|
|
# use mysql;
|
|
|
|
|
# insert into t6 (a) values (3);
|
|
|
|
|
# commit;
|
|
|
|
|
# Transaction3 end
|
|
|
|
|
|
|
|
|
|
--echo #
|
|
|
|
|
--echo # Test if the 'BEGIN', 'ROLLBACK' and 'COMMIT' are output if the database specified is exist
|
2009-09-30 04:31:25 +02:00
|
|
|
|
--exec $MYSQL_BINLOG --database=test --short-form $MYSQLTEST_VARDIR/std_data/binlog_transaction.000001
|
2009-09-30 04:01:52 +02:00
|
|
|
|
--echo #
|
|
|
|
|
--echo # Test if the 'BEGIN', 'ROLLBACK' and 'COMMIT' are output if the database specified is not exist
|
2009-09-30 04:31:25 +02:00
|
|
|
|
--exec $MYSQL_BINLOG --database=not_exist --short-form $MYSQLTEST_VARDIR/std_data/binlog_transaction.000001
|
2009-09-30 04:01:52 +02:00
|
|
|
|
|
2007-02-19 11:57:06 +01:00
|
|
|
|
--echo End of 5.0 tests
|
2009-05-08 19:24:15 +02:00
|
|
|
|
|
2007-03-07 07:21:24 +01:00
|
|
|
|
--echo End of 5.1 tests
|