Debian Codegraph @

mysql-test/suite/innodb_fts/t/fulltext3.test

raw
1 --source include/have_gbk.inc
2 #
3 # test of new fulltext search features
4 #
5 --source include/have_innodb.inc
6 --source include/maybe_versioning.inc
7
8 --disable_warnings
9 DROP TABLE IF EXISTS t1;
10 --enable_warnings
11
12 let $default_engine = `select @@SESSION.default_storage_engine`;
13 #
14 # BUG#29299 - repeatable myisam fulltext index corruption
15 #
16 # INNODB_FTS: Not yet support gbk charset
17 CREATE TABLE t1(a VARCHAR(255) CHARACTER SET gbk, FULLTEXT(a)) ENGINE = InnoDB;
18 SET NAMES utf8;
19 # INSERT INTO t1 VALUES(0xF043616161),(0xBEF361616197C22061616161);
20 # SELECT HEX(a) FROM t1 WHERE MATCH(a) AGAINST(0x97C22061616161 IN BOOLEAN MODE);
21 DELETE FROM t1 LIMIT 1;
22 #CHECK TABLE t1;
23 SET NAMES latin1;
24 DROP TABLE t1;
25
26 # End of 5.0 tests
27
28 #
29 # BUG#29464 - load data infile into table with big5 chinese fulltext index
30 # hangs 100% cpu
31 #
32 --replace_result $default_engine <default_engine>
33 EVAL CREATE TABLE t1(a VARCHAR(2) CHARACTER SET big5 COLLATE big5_chinese_ci,
34 FULLTEXT(a)) ENGINE=$default_engine;
35 # INSERT INTO t1 VALUES(0xA3C2);
36 DROP TABLE t1;
37
38 # End of 5.1 tests
39
40
41 CREATE TABLE t1 (a SERIAL, t TEXT, FULLTEXT f1(t), FULLTEXT f2(t)) ENGINE=InnoDB;
42 INSERT INTO t1 (a,t) VALUES (1,'1'),(2,'1');
43 ALTER TABLE t1 ADD COLUMN g TEXT GENERATED ALWAYS AS (t) VIRTUAL;
44 DELETE FROM t1 WHERE a = 1;
45 ALTER TABLE t1 DROP INDEX f1;
46 INSERT INTO t1 (a,t) VALUES (1,'1');
47 DROP TABLE t1;