JB,
If you are interested (and able to share), send me a dump of your
database off-list. I do a lot of MySQL work and although what you are
doing may be a design limitation, I'd be willing to fiddle with it for
a few minutes, which is infinitely more productive than speculating in
emails =).
- Brian
Hello again,
For those interested in the latest episodes of my struggle with mySQL,
here's a summary : I've tried the MATCH (col1) AGAINST ("word1 word2")
construct, and it's blazing fast (roughly 50 to 100 times faster
than my previous
queries full of OR statements...
But there's a couple of drawbacks : columns on which MATCH.. AGAINST
is
used need to have a fulltext index attached to them (which is
logical), BUT there's
a minimum word length limit on such indexes (default length is 4,
set with a mySQL
global). No wonder it's so fast, since lots of words are ignored...
So, if you need smaller words to become searchable, you need to
modify the
ft_min_word_len global (setting it to 1 if you need all words to be
searchable) and
restart mySQL... and reconstruct your indexes as well.
And then searches via MATCH ... AGAINST become almost as slow as
regular
SELECT searches...
Oh, and I forgot to mention that there's also a list of rejected
words that can be modified
in another global...
JB
_______________________________________________
use-revolution mailing list
[email protected]
Please visit this url to subscribe, unsubscribe and manage your
subscription preferences:
http://lists.runrev.com/mailman/listinfo/use-revolution
_______________________________________________
use-revolution mailing list
[email protected]
Please visit this url to subscribe, unsubscribe and manage your subscription
preferences:
http://lists.runrev.com/mailman/listinfo/use-revolution
