RE: Fulltext searching

I beleive this is the built-in word list file you were looking for. And the word "beyond" was in the list. It would probably be helpful if there were a SHOW command that listed the active built-in stopwords. Ed - #include "ftdefs.h" ulong ft_min_word_len=4; ulong ft_ma

Re: Fulltext searching

on 5/6/04 16:53, Michael Stassen at [EMAIL PROTECTED] wrote: > If you've built from source, the stopwords are in > > path-to-source/myisam/ft_static.c > > In my copy of 4.0.18, beyond is in the list. > > You can create your own stopword list, or turn off stopwords altogether, if > you want. S

Re: Fulltext searching

If you've built from source, the stopwords are in path-to-source/myisam/ft_static.c In my copy of 4.0.18, beyond is in the list. You can create your own stopword list, or turn off stopwords altogether, if you want. See for the detai

Re: Fulltext searching

In my system variables it shown that the stopword file is "(built-in)" so where would I find it then if it is built in.. 'Beyond" does not seem like a word that would be in a built-in stopword file does it? Could it be reserved? Thanks! Rick on 5/6/04 15:30, Dathan Vance Pattishall at [EMAIL

RE: Fulltext searching

Check to see if beyond is in your stopword file. > -Original Message- > From: Richard Baskett [mailto:[EMAIL PROTECTED] > Sent: Thursday, May 06, 2004 2:12 PM > To: MySQL > Subject: Fulltext searching > > Ok having some problems with MySQL's fulltext search. I have the fields > that I ne

Re: fulltext searching

* m n [...] > SELECT * FROM `mytest` WHERE (MATCH (sub) against ("my")); ... and short (default < 4 characters) words are not indexed... http://www.mysql.com/doc/en/Fulltext_Fine-tuning.html > -- Roger -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscri

Re: fulltext searching

"m n" <[EMAIL PROTECTED]> wrote: > How fulltext is working!!? >From the MySQL manual: The search for the word MySQL produces no results in the above example, because that word is present in more than half the rows. As such, it is effectively treated as a stopword (that is, a word with zero sema

Re: fulltext searching

* m n > I have the following table with just one record! And when I do a select > statement, mysql returns no hits!!! > > Would you explain to me what is wrong?? You have only one row. http://www.mysql.com/doc/en/Fulltext_Search.html > "For very small tables, word distribution does not reflect a

Re: FULLTEXT Searching

"Ralph Guzman" <[EMAIL PROTECTED]> wrote: > I have to do a catalog search through multiple tables and columns for > product model number, description, and name. I realize that doing > pattern matching with multiple LIKE statements is slow so I found that > FULLTEXT searches is a better alternative.

Re: FULLTEXT Searching

Ralph Guzman wrote: I have to do a catalog search through multiple tables and columns for product model number, description, and name. I realize that doing pattern matching with multiple LIKE statements is slow so I found that FULLTEXT searches is a better alternative. I have added a FULLTEXT in

RE: fulltext searching and query order question

I think I need to clarify : The fulltext indexing & searching here works great. The search completes in good time, but then I want it in a different order, as described by index1 down below. This resorting step is the one that takes forever, not the fulltext search. So essentially, a FORCE INDEX(

RE: fulltext searching and query order question

Have you tried adding force index on your fulltext index? Something similar to this: select field1,field2,field3 from table FORCE INDEX(index2) where field1='something' and field2='something_else' and field3='something_more' and match(field4) against ('word1 word2' in boolean mode) orde

re: Fulltext searching - getting list of stop words?

Tim, Thursday, September 19, 2002, 1:09:42 PM, you wrote: TF> I'm implementing a search feature on one of my sites and I would like TF> to have a Google-style "X is a very common word and was not included TF> in your search" for stop words. I believe the stop words in fulltext TF> searching are

Re: fulltext searching / BUG report

sergei, no i meant loading it up from raw data again. in the sense, i empty the database, then i have a script which takes a directory full of files and reads them into the database. each time i do that the database ends up corrupted. is there any way to figure out where the corruption is? is it

Re: fulltext searching / BUG report

Hi! On Jul 02, Thomas Spahni wrote: > On Tue, 2 Jul 2002, Erlend Hops? Str?msvik wrote: > > > Download the 4.0.2 source and compile it. > > Things seem to work a lot better with the 4.0.2. And it won't crash with > > special combinations of words :) > > Hi, > > Some things with BOOLEAN MODE s

Re: fulltext searching

> plus are you sure you're reading the latest manual? it is chapter 6.8. The location was correct for the onlien manual. I first tried my stored PDf version, since I could not reach http://www.mysql.com There, it was section 24.2. Now I printed then online section 6.8 and will go through it. My

RE: fulltext searching / BUG report

On Tue, 2 Jul 2002, Erlend Hopsø Strømsvik wrote: > Download the 4.0.2 source and compile it. > Things seem to work a lot better with the 4.0.2. And it won't crash with > special combinations of words :) Hi, Some things with BOOLEAN MODE seem still broken. Especially the '*' jokers. I have 4.

Re: fulltext searching

plus are you sure you're reading the latest manual? it is chapter 6.8. try this (google cache of the mysql.com/doc since mysql.com seems to be down): http://www.google.com/search?q=cache:yvsB86pbs5cC:www.mysql.com/doc/F/u/Fulltext_Search.html+full+text+mysql&hl=en&ie=UTF-8 ciao, m. Quoting "E

Re: fulltext searching

there's not a huge lot more to cover than what is in the manual... what exactly are you looking for? m. Quoting "Eivind A. Sivertsen" <[EMAIL PROTECTED]>: > > section 6.8 in the manual i think... > > Hmm, no; that's about the access privilege system... > I found it in section 24.2, but I feel

Re: Re: fulltext searching

Eivind, Tuesday, July 02, 2002, 12:22:33 PM, you wrote: EAS> Is there a tutorial or step-by-step introduction to fulltext searches with EAS> MySQL somewhere? Sure. In the MySQL manual: http://www.mysql.com/doc/F/u/Fulltext_Search.html -- For technical support contracts, goto https://

Re: fulltext searching

> section 6.8 in the manual i think... Hmm, no; that's about the access privilege system... I found it in section 24.2, but I feel this topic has gotten a bit scarce mention in the manual. Perhaps it deserves more than that...? I sure would appreciate something extra <:-) Best regards,

RE: fulltext searching

Hi If anybody from mysql is listening / watching, www.mysql.com is down, and has been for a while. Peter --- Excellence in internet and open source software --- Sunmaia www.sunmaia.net [EMAIL PROTECTED] te

Re: fulltext searching

section 6.8 in the manual i think... Quoting "Eivind A. Sivertsen" <[EMAIL PROTECTED]>: > Is there a tutorial or step-by-step introduction to fulltext searches with > MySQL somewhere? > > Regards, > > Eivind :-o > > > > -

Re: fulltext searching

Is there a tutorial or step-by-step introduction to fulltext searches with MySQL somewhere? Regards, Eivind :-o - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.

RE: fulltext searching

hings seem to work a lot better with the 4.0.2. And it won't crash with special combinations of words :) Erlend Stromsvik -Original Message- From: Marko Djukic [mailto:[EMAIL PROTECTED]] Sent: 1. juli 2002 12:43 To: [EMAIL PROTECTED] Subject: Re: fulltext searching hi all... i can

Re: fulltext searching

Hi! On Jul 01, Marko Djukic wrote: > i can't seem to get the fulltext searching working perfectly... single > search terms it works fine, multiple search terms it also seems to be > ok - finding records with any of the search terms. however, if i try > the boolean mode it gives out garbage all t

Re: fulltext searching

hi all... i can't seem to get the fulltext searching working perfectly... single search terms it works fine, multiple search terms it also seems to be ok - finding records with any of the search terms. however, if i try the boolean mode it gives out garbage all the time. i try for example an s