dbTalk Databases Forums  

MATCH ... AGAINST not working as expected

comp.databases.mysql comp.databases.mysql


Discuss MATCH ... AGAINST not working as expected in the comp.databases.mysql forum.



Reply
 
Thread Tools Display Modes
  #11  
Old   
Álvaro G. Vicario
 
Posts: n/a

Default Re: MATCH ... AGAINST not working as expected - 01-17-2011 , 05:51 AM






El 17/01/2011 11:29, Erick T. Barkhuis escribió/wrote:
Quote:
"Álvaro G. Vicario":

El 17/01/2011 9:27, Erick T. Barkhuis escribió/wrote:

If "the" is ignored because it has only three characters, why is it
on the default stopword list?

The OP's example illustrates this just fine: he'll probably consider
to lower the character length so he's able to find "fun", but I don't
think he's specially interested in "the".

So, he doesn't include "the" in his search phrase.

They're just similar concepts that MySQL allows to be handled
separately.

In a way, I understand this.
Yet, if someone isn't interested in stopwords, why would [s]he include
them in the query?
When you google for "What's the population of Coventry?" none of the two
first entries include this exact phrase, yet both contain the
information you are looking for. That's the idea of full text search.

If you are referring to the "+" operator then you're right: if I type
"+the" I'm asking for results that _do_ contain "the". The answer of why
it's omitted from search is probably a technical one: min char limit and
stop words are used to keep the index size manageable. Being able to
skip them would mean that MySQL should always create a full size index
and would reduce overall performance.



--
-- http://alvaro.es - Álvaro G. Vicario - Burgos, Spain
-- Mi sitio sobre programación web: http://borrame.com
-- Mi web de humor satinado: http://www.demogracia.com
--

Reply With Quote
  #12  
Old   
EastSideDev
 
Posts: n/a

Default Re: MATCH ... AGAINST not working as expected - 01-17-2011 , 07:21 AM






On Jan 17, 2:21*am, "Álvaro G. Vicario"
<alvaro.NOSPAMTH... (AT) demogracia (DOT) com.invalid> wrote:
Quote:
El 17/01/2011 9:27, Erick T. Barkhuis escribió/wrote:



"Álvaro G. Vicario":

El 16/01/2011 1:19, EastSideDev escribió/wrote:

SELECT * FROM `table` WHERE MATCH (Description) AGAINST ('+party
+fun +town' IN BOOLEAN MODE)

"fun" is probably being ignored because of its 3 char length:
* Any word that is too short is ignored. The default minimum length
of words that are found by full-text searches is four characters.

*Words in the stopword list are ignored. A stopword is a word such as
“the” or “some” that is so common that ...»

If "the" is ignored because it has only three characters, why is it on
the default stopword list?

The OP's example illustrates this just fine: he'll probably consider to
lower the character length so he's able to find "fun", but I don't think
he's specially interested in "the".

They're just similar concepts that MySQL allows to be handled separately.

--
--http://alvaro.es- Álvaro G. Vicario - Burgos, Spain
-- Mi sitio sobre programación web:http://borrame.com
-- Mi web de humor satinado:http://www.demogracia.com
--
I will lower the minimum search term to 3 letters instead of 4. The
entry form is web-based, so I have no control over what users will
enter, and I don't expect them to understand concepts like stop-words
as a pre-requisite to improve overall system performance, or why words
like "fun", or "ice", or "pub" cannot be included.

Reply With Quote
  #13  
Old   
Erick T. Barkhuis
 
Posts: n/a

Default Re: MATCH ... AGAINST not working as expected - 01-17-2011 , 07:22 AM



EastSideDev:

Quote:
and I don't expect them to understand concepts like stop-words
as a pre-requisite to improve overall system performance, or why words
like "fun", or "ice", or "pub" cannot be included.
Well, "pub" is definitely a stop-word! :-)

Reply With Quote
Reply




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off



Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.