A glaring bug in FULLTEXT search?

Here's a transcript of my chat with mysql:

----------------------
mysql> create table test (id int, name text, fulltext nameidx(name))
type=MyISAM;
Query OK, 0 rows affected (0.10 sec)

mysql> insert into test values (1, 'some words');
Query OK, 1 row affected (0.06 sec)

mysql> insert into test values (2, 'other words');
Query OK, 1 row affected (0.00 sec)

mysql> select * from test;
+------+-------------+
| id   | name        |
+------+-------------+
|    1 | some words  |
|    2 | other words |
+------+-------------+
2 rows in set (0.10 sec)

mysql> select * from test where match(name) against('word');
Empty set (0.02 sec)

mysql> select * from test where match(name) against('words');
Empty set (0.00 sec)

mysql> select * from test where match(name) against('some');
Empty set (0.00 sec)

mysql> select * from test where match(name) against('other');
Empty set (0.00 sec)
-------------------------------

Is this a bug or am I misunderstanding how FULLTEXT search is supposed to work?


--
Makefiles not war





-- 
MySQL Bugs Mailing List
For list archives: http://lists.mysql.com/bugs
To unsubscribe:    http://lists.mysql.com/[email protected]