As of version 3.23.33 MySQL became attractive to deploy in our project
because it now includes (preliminary, though) support for full text
indeces. That is a GREAT advantage to prior versions. So,
congratulations for that feature, with that MySQL is definititly moving
on the right path and I'm very sure FULLTEXT is among the most important
feature why people decide to make use of MySQL.
Now, unfortunately the FULLTEXT support as it stands right now has a few
drawbacks (all my tests where done with 3.23.33 and ~ 200000 rows (~
60MB) in my test table.:
- searches for words with hits < 100 are reasonably fast (<1 sec.)
- searches with hits > 100 can get REALLY slow.:
4538 rows in 12.19 sec: select id from axp_bild where match(caption_de,
caption_us, caption_fr) against ('Kohl');
4998 rows in 6.09 sec: select id from axp_bild where upper(caption_de)
like '%KOHL%' or upper(caption_us) like '%KOHL%' or upper(caption_fr)
like '%KOHL%';
-> mmhhh.... that makes me nervous! The FULLTEXT slower than full table
scan?
- The default for searches like "against ('Aaaaa Bbbbb')" is to "OR" A
and B, but it would be MUCH more usable to have it to "AND" A and B by
default.
Regards,
;Martin
---------------------------------------------------------------------
Before posting, please check:
http://www.mysql.com/manual.php (the manual)
http://lists.mysql.com/ (the list archive)
To request this thread, e-mail <[EMAIL PROTECTED]>
To unsubscribe, e-mail <[EMAIL PROTECTED]>
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
