had a quick look... it does queries that open the table twice, so can't temporary table. There's a key on another table, which rules archive out. too big for heap.
but.... a comment in the include file for the test only suggests that the engines should be different... and from looking at the queries, i think it's okay to do that. the comment (include/read_many_rows.inc): # include/read_many_rows.inc # # Test how filesort and buffered-record-reads works # This test needs a lot of time. # # The variables # $engine_type -- storage engine to be tested # $other_engine_type -- storage engine <> $engine_type, if possible # 1. $other_engine_type must allow to store many rows # without using non standard server options # (does not need a t/read_many_rows_*-master.opt file) # 2. $other_engine_type must point to an all time # available storage engine # 2006-08 MySQL 5.1 MyISAM and MEMORY only # have to be set before sourcing this script. # # Last update: # 2006-08-03 ML test refactored (MySQL 5.1) # main code t/innodb-big.test --> include/read_many_rows.inc # -- Stewart Smith _______________________________________________ Mailing list: https://launchpad.net/~drizzle-discuss Post to : [email protected] Unsubscribe : https://launchpad.net/~drizzle-discuss More help : https://help.launchpad.net/ListHelp
