mirror of
https://github.com/MariaDB/server.git
synced 2025-01-28 01:34:17 +01:00
068478fbbf
main.mysqlbinlog_row_innodb are skipped by mtr === Problem === The following tests are wrongly placed in main suite and as a result these are not run with proper binlog format combinations. Some are always skipped by mtr. 1) mysqlbinlog_row_myisam 2) mysqlbinlog_row_innodb 3) mysqlbinlog_row.test 4) mysqlbinlog_row_trans.test 5) mysqlbinlog-cp932 6) mysqlbinlog2 7) mysqlbinlog_base64 === Background === mtr runs the tests placed in main suite with binlog format=stmt. Those that need to be tested against binlog format=row or mixed or more than one binlog format and require only one mysql server are placed in binlog suite. mtr runs tests in binlog suite with all three binlog formats(stmt,row and mixed). === Fix === 1) Moved the test listed in problem section above to binlog suite. 2) Added prefix "binlog_" to the name of each test case moved. Renamed the coresponding result files and option files accordingly.
23 lines
631 B
Text
23 lines
631 B
Text
# mysqlbinlog_row.test
|
|
#
|
|
# Show that mysqlbinlog displays human readable comments to
|
|
# row-based log events.
|
|
#
|
|
# Main module for the MyISAM storage engine.
|
|
#
|
|
# Calls include/mysqlbinlog_row.inc
|
|
# See there for more informaton.
|
|
#
|
|
|
|
#--source include/have_myisam.inc
|
|
let $engine_type=MyISAM;
|
|
|
|
#
|
|
# The test case would also work with statement based or mixed mode logging.
|
|
# But this would require different result files. To handle this with the
|
|
# current test suite, new main test cases are required.
|
|
#
|
|
--source include/have_binlog_format_row.inc
|
|
--source include/have_ucs2.inc
|
|
|
|
--source extra/binlog_tests/mysqlbinlog_row_engine.inc
|