mirror of
				https://github.com/MariaDB/server.git
				synced 2025-11-03 14:33:32 +03:00 
			
		
		
		
	and small collateral changes mysql-test/lib/My/Test.pm: somehow with "print" we get truncated writes sometimes mysql-test/suite/perfschema/r/digest_table_full.result: md5 hashes of statement digests differ, because yacc token codes are different in mariadb mysql-test/suite/perfschema/r/dml_handler.result: host table is not ported over yet mysql-test/suite/perfschema/r/information_schema.result: host table is not ported over yet mysql-test/suite/perfschema/r/nesting.result: this differs, because we don't rewrite general log queries, and multi-statement packets are logged as a one entry. this result file is identical to what mysql-5.6.5 produces with the --log-raw option. mysql-test/suite/perfschema/r/relaylog.result: MariaDB modifies the binlog index file directly, while MySQL 5.6 has a feature "crash-safe binlog index" and modifies a special "crash-safe" shadow copy of the index file and then moves it over. That's why this test shows "NONE" index file writes in MySQL and "MANY" in MariaDB. mysql-test/suite/perfschema/r/server_init.result: MariaDB initializes the "manager" resources from the "manager" thread, and starts this thread only when --flush-time is not 0. MySQL 5.6 initializes "manager" resources unconditionally on server startup. mysql-test/suite/perfschema/r/stage_mdl_global.result: this differs, because MariaDB disables query cache when query_cache_size=0. MySQL does not do that, and this causes useless mutex locks and waits. mysql-test/suite/perfschema/r/statement_digest.result: md5 hashes of statement digests differ, because yacc token codes are different in mariadb mysql-test/suite/perfschema/r/statement_digest_consumers.result: md5 hashes of statement digests differ, because yacc token codes are different in mariadb mysql-test/suite/perfschema/r/statement_digest_long_query.result: md5 hashes of statement digests differ, because yacc token codes are different in mariadb mysql-test/suite/rpl/r/rpl_mixed_drop_create_temp_table.result: will be updated to match 5.6 when alfranio.correia@oracle.com-20110512172919-c1b5kmum4h52g0ni and anders.song@greatopensource.com-20110105052107-zoab0bsf5a6xxk2y are merged mysql-test/suite/rpl/r/rpl_non_direct_mixed_mixing_engines.result: will be updated to match 5.6 when anders.song@greatopensource.com-20110105052107-zoab0bsf5a6xxk2y is merged
		
			
				
	
	
		
			50 lines
		
	
	
		
			1.3 KiB
		
	
	
	
		
			Plaintext
		
	
	
	
	
	
			
		
		
	
	
			50 lines
		
	
	
		
			1.3 KiB
		
	
	
	
		
			Plaintext
		
	
	
	
	
	
# binlog disabled in embedded server
 | 
						|
-- source include/not_embedded.inc
 | 
						|
 | 
						|
# part of sp_trans test that appeared to be sensitive to binlog format
 | 
						|
--source include/have_innodb.inc
 | 
						|
--source include/have_binlog_format_mixed.inc
 | 
						|
 | 
						|
delimiter |;
 | 
						|
 | 
						|
#
 | 
						|
# Bug#13270 INSERT,UPDATE,etc that calls func with side-effect does not binlog
 | 
						|
# Bug#23333 stored function + non-transac table + transac table =
 | 
						|
#           breaks stmt-based binlog
 | 
						|
# Bug#27395 OPTION_STATUS_NO_TRANS_UPDATE is not preserved at the end of SF()
 | 
						|
#
 | 
						|
--disable_warnings
 | 
						|
drop function if exists bug23333|
 | 
						|
drop table if exists t1,t2|
 | 
						|
--enable_warnings
 | 
						|
CREATE TABLE t1 (a int  NOT NULL auto_increment primary key) ENGINE=MyISAM|
 | 
						|
CREATE TABLE t2 (a int  NOT NULL auto_increment, b int, PRIMARY KEY (a)) ENGINE=InnoDB|
 | 
						|
 | 
						|
insert into t2 values (1,1)|
 | 
						|
 | 
						|
create function bug23333() 
 | 
						|
RETURNS int(11)
 | 
						|
DETERMINISTIC
 | 
						|
begin
 | 
						|
  insert into t1 values (null);
 | 
						|
  select count(*) from t1 into @a;
 | 
						|
  return @a;
 | 
						|
end|
 | 
						|
delimiter ;|
 | 
						|
 | 
						|
reset master;
 | 
						|
--error ER_DUP_ENTRY
 | 
						|
insert into t2 values (bug23333(),1);
 | 
						|
# the following must show there are events after the query
 | 
						|
# the binlog_limit is used to hide the differences between the mixed
 | 
						|
# and row logging formats after BUG#53259
 | 
						|
let $binlog_limit= 0, 4;
 | 
						|
source include/show_binlog_events.inc;
 | 
						|
select count(*),@a from t1 /* must be 1,1 */;
 | 
						|
 | 
						|
 | 
						|
# clean-up
 | 
						|
 | 
						|
drop table t1,t2;
 | 
						|
drop function if exists bug23333;
 |