mariadb/mysql-test/t/mix2_myisam.test
mleich@three.local.lan 1a8c9130db This changeset belongs to
WL#3397 Refactoring storage engine test cases (for falcon)
      It contains fixes according to second code review.
- Remove any occurence of hardcoded assignments of storage engines
- Use variable names exact telling what it is used for
- Updated comments
- remove trailing spaces
2006-08-16 19:29:49 +02:00

26 lines
864 B
Text

# t/mix2_myisam.test
#
# Last update: 2006-07-26 ML create this test as derivate from innodb.test
#
let $engine_type= MyISAM;
let $other_engine_type= MEMORY;
# There are unfortunately only MyISAM and MEMORY all time available
# Therefore use here MEMORY again.
let $other_engine_type1= MEMORY;
let $other_non_trans_engine_type= MEMORY;
let $other_non_live_chks_engine_type= MEMORY;
# Therefore use here MyISAM again.
let $other_live_chks_engine_type= MyISAM;
# MyISAM does not support transactions
let $test_transactions= 0;
# MyISAM does not support FOREIGN KEYFOREIGN KEYs
let $test_foreign_keys= 0;
# MyISAM supports fulltext queries
let $fulltext_query_unsupported= 0;
# MyISAM internal autoincrement values are updated during updates
let $no_autoinc_update= 0;
# MyISAM supports keys on spatial data types
let $no_spatial_key= 0;
-- source include/mix2.inc