Hi!
On Feb 27, Haitao Jiang wrote:
>
> Thanks! That was what I guessed. But how to explain
> "16-bit Touch" doesn't match records with "32-bit
> Touch" in the keywords? It just returned all the
> records with "16-bit Touch", i.e. "16-bit" seems does
> count.
Because the presense of "16-bit" substring is verified as a
post-processing. Similar to
MATCH ... AGAINST ('touch') AND ... LIKE '%16-bit%'
and if you'd have min_word_len=3 the query would be executed
similar to
MATCH ... AGAINST ('+touch +bit') AND ... LIKE '%16-bit%'
that is rows would be selected based on an index lookup for two words,
and as a post-processing a substring search would filter out rows
without "16-bit" substring.
Regards,
Sergei
--
__ ___ ___ ____ __
/ |/ /_ __/ __/ __ \/ / Sergei Golubchik <[EMAIL PROTECTED]>
/ /|_/ / // /\ \/ /_/ / /__ MySQL AB, Senior Software Developer
/_/ /_/\_, /___/\___\_\___/ Osnabrueck, Germany
<___/ www.mysql.com
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
