Nitzan, In the unlikely event that you can recompile but not upgrade, you could add your common words to the full text stopword list in myisam/ft_static.c and rebuild mysql.
Otherwise, this might be helpful http://lists.mysql.com/mysql/132649 Andy > -----Original Message----- > From: nitzan shaked [mailto:[EMAIL PROTECTED] > Sent: 22 September 2005 14:57 > To: mysql@lists.mysql.com > Subject: Fulltext behavior in 3.23.58 > > ... this one is peculiar, and I *do* hope there's a workaround: > > Using MySQL 3.23.58 and cannot upgrade. When running "SELECT * FROM > tblname WHERE match(a) against('very_common_word') LIMIT 1" the whole > table is scanned just to give me no results at all. The very common word > *does* appear, and appears in more than 50% of the lines. > > However, I would think that there is no need to scan the whole table just > for that. In MySQL4 the result comes out much quicker, but still very > slowly. > > To contrast, if I use "a_non_existent_word" instead of > "a_very_common_word" I get 0 rows immeidately. If I use > "an_existing_but_not_common_word" I get 1 row quickly: not immeidately as > a non-existing row, but not so slowly as a very common word. > > Questions: > 1) Why the different behavior between MySQL 3 and 4 ? > 2) How to circumnavigate in MySQL 3? > > tia, > Nitzan > > > -- > MySQL General Mailing List > For list archives: http://lists.mysql.com/mysql > To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED] -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
