Edit File: fulltext3.test
--source include/have_gbk.inc # # test of new fulltext search features # --disable_warnings DROP TABLE IF EXISTS t1; --enable_warnings let $default_engine = `select @@SESSION.default_storage_engine`; # # BUG#29299 - repeatable myisam fulltext index corruption # # INNODB_FTS: Not yet support gbk charset CREATE TABLE t1(a VARCHAR(255) CHARACTER SET gbk, FULLTEXT(a)) ENGINE = InnoDB; SET NAMES utf8; # INSERT INTO t1 VALUES(0xF043616161),(0xBEF361616197C22061616161); # SELECT HEX(a) FROM t1 WHERE MATCH(a) AGAINST(0x97C22061616161 IN BOOLEAN MODE); DELETE FROM t1 LIMIT 1; #CHECK TABLE t1; SET NAMES latin1; DROP TABLE t1; # End of 5.0 tests # # BUG#29464 - load data infile into table with big5 chinese fulltext index # hangs 100% cpu # --replace_result $default_engine <default_engine> EVAL CREATE TABLE t1(a VARCHAR(2) CHARACTER SET big5 COLLATE big5_chinese_ci, FULLTEXT(a)) ENGINE=$default_engine; # INSERT INTO t1 VALUES(0xA3C2); DROP TABLE t1; # End of 5.1 tests