Details
-
Bug
-
Status: Closed (View Workflow)
-
Minor
-
Resolution: Fixed
-
10.0.3, 5.5.31, 5.1.67, 5.2.14, 5.3.12
-
None
-
None
Description
The following queries produce ER_FT_MATCHING_KEY_NOT_FOUND (Can't find FULLTEXT index matching the column list) although the table t1 clearly has a fulltext index, and there is only one column there.
I'm not marking this as 'upstream', because the story is vague. On MySQL, it works fine on 5.1, fails in the same manner on 5.5, and works again on 5.6. But on MariaDB, it fails on all of 5.1, 5.2, 5.3, 5.5, 10.0; so maybe the problem in MariaDB is independent from whatever changes are made in MySQL.
create table t1 (a text, fulltext index (a)) engine=MyISAM; |
insert into t1 values ('MySQL'); |
( select a from t1 order by match (a) against ('MySQL') ) order by a; |
( select a from t1 order by match (a) against ('MySQL') ) union ( select 'abc' ); |
Output:
MariaDB [test]> create table t1 (a text, fulltext index (a)) engine=MyISAM;
|
Query OK, 0 rows affected (0.20 sec)
|
|
|
MariaDB [test]> insert into t1 values ('MySQL');
|
Query OK, 1 row affected (0.00 sec)
|
|
|
MariaDB [test]> ( select a from t1 order by match (a) against ('MySQL') ) order by a;
|
ERROR 1191 (HY000): Can't find FULLTEXT index matching the column list
|
|
|
MariaDB [test]> ( select a from t1 order by match (a) against ('MySQL') ) union ( select 'abc' );
|
ERROR 1191 (HY000): Can't find FULLTEXT index matching the column list
|