1
0
mirror of https://github.com/MariaDB/server.git synced 2025-07-29 05:21:33 +03:00

BUG#40707 rpl_multi_engine fails sporadically in pushbuild

If before running test rpl_mulit_engin, the mysqltest1 database exists
on master but not exists on slave, then the following statement:

  create database if not exists mysqltest1;

would not be logged to binary log, and so the database would not be
created on slave. This would cause the test to fail and reporting 
mysqltest1 database not existed on slave.

This patch fixed this problem by not using a different database for
the whole test, just use the default test database, there is no reason
why a seperate database is used for this test.


mysql-test/include/rpl_multi_engine.inc:
  use default test database instead of mysqltest1
mysql-test/suite/rpl/r/rpl_multi_engine.result:
  use default test database instead of mysqltest1
mysql-test/suite/rpl/t/rpl_multi_engine.test:
  use default test database instead of mysqltest1
  add missing --enable_warnings
This commit is contained in:
He Zhenxing
2008-11-24 14:57:23 +08:00
parent ab0e404c73
commit 5676a2d770
3 changed files with 11 additions and 19 deletions

View File

@ -12,16 +12,14 @@ connection slave;
connection master;
-- source include/have_innodb.inc
--disable_warnings
create database if not exists mysqltest1;
use mysqltest1;
drop table if exists t1;
--enable_warnings
CREATE TABLE t1 (id MEDIUMINT NOT NULL, b1 BIT(8), vc
VARCHAR(255), bc CHAR(255), d DECIMAL(10,4) DEFAULT 0, f FLOAT DEFAULT
0, total BIGINT UNSIGNED, y YEAR, t TIMESTAMP,PRIMARY KEY(id));
sync_slave_with_master;
use mysqltest1;
# MyISAM to MyISAM then InnoDB then MEMORY
@ -101,8 +99,6 @@ show create table t1;
# cleanup
connection master;
DROP TABLE t1;
# Need to drop mysqltest1 as well so other test will pass.
DROP DATABASE mysqltest1;
sync_slave_with_master;
# End of 5.1 test case