I know that the web-page says it may return bizzare results in small
cases, but I would have expected it to return consistant results though.
I came across this due to an inconsistancy that I ran across in an
application that I've been working on.
One of the fields I have defined as a tinytext, and the data in there is
a set of identifiers which are comma seperated.(each identifier is 4
characters long) ~68000 records in the table, there are > 64 different
identifiers so I assume that I can't use a set.
So the crux of the problem is that when the identifiers are all the
same, they become 'stop-words' and nothing is returned from the queries.
Is there a way to disable the stop-words in the fulltext indexing?
If there isn't a way to disable the stop-words, is doing a 'LIKE' or
'RLIKE' even moderately compariable speed-wise, my quick tests show that
it isn't even close (1.32 and 1.57 sec vs 0.11 sec), but if it's going
to start ignoring the most common identifiers in the database, it's
unacceptable, and I'll need to live with the slowdown.
Thanks for any advice
Scott V
---------------------------------------------------------------------
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
