Hi David,

Try here
http://dev.mysql.com/doc/refman/5.1/en/fulltext-fine-tuning.html
There are system vars:

[mysqld]
ft_min_word_len=3

Google gave up some fulltext plugins for mysql to replace the default one.
Apparantly you can invoke plugins on a query by query basis
http://dev.mysql.com/doc/refman/5.1/en/plugin-full-text-plugins.html

I am only talking the talk here but I am interested in the possibilities 
of Extended Boolean searches for mySQL,
EB is a very promising technology that is much better than the 
all-or-nothing hits you get with boolean methods.
Actually I can predict that the capability to EB searches will 
eventually impact on web design,
and I would think that "Semantic Markup" will then allow you to apply 
these kinds of searches to your XML docs as well..

Keith





David wrote:
> Thanks for the suggestions. Will have to play around with this a bit
> and see which works best in our situation. I'm somewhat tempted to
> switch over to Lucene eventually as I am more familiar with that.
> However, MySQL's full text search seems to work pretty well. Thanks
> again!
>
> David
>
> On Jun 27, 11:12 pm, Steve Wake <[email protected]> wrote:
>   
>> Also, if you use boolean mode, it helps to prepend all words with a +  
>> (including the first) or it can use the first as an 'or'.
>>
>> On 26/06/2009, at 9:59 AM, Matias Gertel wrote:
>>
>>
>>
>>     
>>> Hi David,
>>> You may want to try the "IN BOOLEAN MODE" modifier. If you prepend  
>>> the short words and/or stopwords with a + mysql will still search  
>>> for them. It works differently than the regular fulltext search, so  
>>> you'll have to play with it to make sure the results are still  
>>> relevant.
>>> http://dev.mysql.com/doc/refman/5.1/en/fulltext-boolean.html
>>>       
>>> Matias Gertel
>>> Freelance Web Development & Coding
>>> e: [email protected]
>>> m: +64 21 288 8840
>>> p: +64 9 838 3367
>>>       
>>> On 26/06/2009, at 7:30 AM, Berend de Boer wrote:
>>>       
>>>>>>>> "David" == David  <[email protected]> writes:
>>>>>>>>                 
>>>    David> Perhaps I should allow 2-3 character terms and just parse
>>>    David> out stop words, but this may be an overly complex solution
>>>    David> to a simple problem.
>>>       
>>> MySQL has a list of stop words I believe. I remember vaguely it is
>>> hard to change, but I'm always on 3 character words, and this doesn't
>>> appear to be a problem.
>>>       
>>> --
>>> Cheers,
>>>       
>>> Berend de Boer
>>>       
> >   
> ------------------------------------------------------------------------
>
>
> No virus found in this incoming message.
> Checked by AVG - www.avg.com 
> Version: 8.5.375 / Virus Database: 270.12.94/2207 - Release Date: 06/28/09 
> 17:54:00
>
>   


--~--~---------~--~----~------------~-------~--~----~
NZ PHP Users Group: http://groups.google.com/group/nzphpug
To post, send email to [email protected]
To unsubscribe, send email to
[email protected]
-~----------~----~----~----~------~----~------~--~---

Reply via email to