Guys,
I doubt I'd qualify as an expert but here's my two pence worth ( ;^)
)I wrote a search engine a while back that relies heavily on full-text
searching and the three things I found that improved results were...
1) Precisely what Dan explains, doing extra biasing per field in the SQL
wi
In the last episode (Jan 31), Mike Morton said:
> Mike:
>
> :) I wish! Free ham for everyone!
>
> I had already changed the min length to 2 actually - so that is not the
> affecting factor...
>
> It is more of an issue to prioritizing fields for relevance, and whether it
> is possible to do th
Mike:
:) I wish! Free ham for everyone!
I had already changed the min length to 2 actually - so that is not the
affecting factor...
It is more of an issue to prioritizing fields for relevance, and whether it
is possible to do this within a fulltext query, or whether it needs to be
done through
Mike,
It's likely because MySQL fulltext index defaults to a word length
of 4 characters or more. So "Ham" probably is not being indexed. You will
need to change the minimum word length. See
http://dev.mysql.com/doc/refman/5.0/en/fulltext-fine-tuning.html
Mike
(P.S. Send me a free ham
Does anyone have any suggestions on how to solve the result weighting
problem? I have a client whose search results are becoming more and more
important, and the relevance demands on the results are not entirely
satisfactory...
The fields that are searched are code, name, small description and lar
