RE: fulltext search option

So far as I know, the only way to accomplish what you want is to do what you tried: put the Boolean match in the WHERE clause and order by a natural match. That's what I do on our web site. By the way, you can't use prefix stemming: "*abcd" is the same as "abcd". Regards, Jerry Schwartz The Info

RE: Fulltext search dilemma (IN BOOLEAN MODE) [RESOLVED]

pened, the server was always shut down properly. -Andy -Original Message- From: Jerry Schwartz [mailto:[EMAIL PROTECTED] Sent: Thursday, February 01, 2007 4:10 PM To: Andreas Iwanowski Cc: mysql@lists.mysql.com Subject: RE: Fulltext search dilemma (IN BOOLEAN MODE) Sorry, I have no idea wh

RE: Fulltext search dilemma (IN BOOLEAN MODE)

1, 2007 2:22 PM > To: Jerry Schwartz > Cc: mysql@lists.mysql.com > Subject: RE: Fulltext search dilemma (IN BOOLEAN MODE) > > Hi, thank you for your reply. > > I have used the option ft_min_word_len=3. > If I have something like > 1. "Key West" > in the dat

RE: Fulltext search dilemma (IN BOOLEAN MODE)

[EMAIL PROTECTED] Sent: Thursday, February 01, 2007 1:52 PM To: Andreas Iwanowski; mysql@lists.mysql.com Subject: RE: Fulltext search dilemma (IN BOOLEAN MODE) Unless you changed the minimum word length, "Key" would be ignored because it is too short. I would think the quotation marks at the

RE: Fulltext search dilemma (IN BOOLEAN MODE)

Unless you changed the minimum word length, "Key" would be ignored because it is too short. I would think the quotation marks at the start or end of the words would be ignored. The asterisk operator is only valid at the end of a word. Those initial asterisks, and the quotation marks, would be treat

Re: fulltext search optimization

ong. You might as well be searching on LIKE "%.mp3%", probably would be about just as fast, and you could use a memory table if you wanted. - Original Message - From: "Svilen Spasov (Ancient Media)" <[EMAIL PROTECTED]> To: Sent: Thursday, July 13, 2006 9:57 AM Su

Re: fulltext search optimization

Thanks for your respond. Here is the CREATE TABLE: CREATE TABLE `results_1` ( `id` int(11) NOT NULL auto_increment, `filename` varchar(255) collate cp1251_bulgarian_ci default NULL, `fileext` varchar(10) collate cp1251_bulgarian_ci default NULL, `username` varchar(16) collate cp1251_bulg

Re: fulltext search optimization

Svilen Spasov (Ancient Media) wrote: Hello, I have a website with a MySQL database and I have a table with ~2 millions row (usernames, filenames; ~120MB db data file and ~230MB db index file) with I would like to search using the fulltext indeces. Unfortunately the server get loaded pretty m

Re: Fulltext search for term 'c++'

I think the '+' will not get into the index in the first place. So, there's probably no way to get a search to use the index. However if you want a consistant query format for your search you could probably get the correct result by wrapping the search term in double quotes: select f1 from t1 w

Re: fulltext search

On Sun, 18 Dec 2005, Octavian Rasnita wrote: > Hi, > > Please tell me how can I configure MySQL 5 in order to be able to search > (using fulltext indexes) for combined words like "s-au". > > This is a single word and not 2 words but I think MySQL thinks that there > are 2 words, one of them having

Re: fulltext search

> AFAIK you are right - MySQL treats a hypen as a word-break. And, AFAIK you cannot modify that behaviour. > > The only possibility, I think, would be to modify the source and compile your own MySQL. :-( > > However if you do a full-text search using IN BOOLEAN MODE, then you can put quotes arou

Re: fulltext search

AFAIK you are right - MySQL treats a hypen as a word-break. And, AFAIK you cannot modify that behaviour. The only possibility, I think, would be to modify the source and compile your own MySQL. :-( However if you do a full-text search using IN BOOLEAN MODE, then you can put quotes around hype

Re: fulltext search on words inside words

Merlin wrote: I am wondering if it is possible to find words inside words with the help of fulltext search. Is this possible? Google does that, so somehow there should be a way. Somehow I don't think that Google runs on a single MySQL database. Full text indexes in MySQL mean that "words" (My

Re: FULLTEXT search result requirement

2005/8/11, Eric Jensen <[EMAIL PROTECTED]>: > I am looking into using the FULLTEXT search features for our FAQ > system. Problem is the 50% limitation. We aren't going to have > thousands of questions or articles, so the odds of most of the > questions/articles matching is high and a desireable e

RE: Fulltext search question

[snip] Given a search string of 'NA&SD' my default Fulltext search doesn't find it. Wondered why? [/snip] Quote from http://dev.mysql.com/doc/mysql/en/Fulltext_Search.html: "MySQL uses a very simple parser to split text into words. A "word" is any sequence of true word characters (letters, digits

Re: Fulltext search string less than 4 characters

Lee, establish the fulltext minimum word length system variable as follows... [mysqld] ft_min_word_len=3 reference: http://dev.mysql.com/doc/mysql/en/Fulltext_Fine-tuning.html cheers, --bemansell Brian E. Mansell MySQL Professional On Thu, 06 Jan 2005 20:59:23 -0500, leegold <[EMAIL PROTEC

Re: Fulltext search Strategy - Need Help

Search '+ford +focus' [in boolean mode] Santino At 13:22 + 3-11-2004, Lee Denny wrote: Hello, I'm doing fairly straight forward fulltext searches, but I want to nest them - basically do a keyword search on 'phrase 1' and then search the results this returns for 'phrase 2', for example if phrase

RE: Fulltext Search help

On Fri, 15 Oct 2004 20:05:57 -0400, "leegold" <[EMAIL PROTECTED]> said: > > On Fri, 15 Oct 2004 15:00:10 -0700, "Chris W. Parker" ... But maybe there's a better way? I > wish I could do *searchstring* in Fulltext even if the speed was slow as > molasass it's the spec the user wants. Of cours

RE: Fulltext Search help

Try to search in keyword table: select * from keywords WHERE MATCH(keyword_txt) AGAINST ('$radio_keyword' IN BOOLEAN MODE); If it works the problem is in the join. Santino $query = "SELECT page.* FROM `page` LEFT JOIN `keywords` USING (`page_id`) WHERE MATCH (`keywords`.`keyword_txt`) AGAINST ('$

RE: Fulltext Search help

On Fri, 15 Oct 2004 15:00:10 -0700, "Chris W. Parker" <[EMAIL PROTECTED]> said: > leegold > on Friday, October 15, 2004 2:32 PM said: > > > I do fulltext search on "work". And AFAIK the search will not find > > "work". For that matter the seach will not find "ingm".

RE: Fulltext Search help

leegold on Friday, October 15, 2004 2:32 PM said: > I do fulltext search on "work". And AFAIK the search will not find > "work". For that matter the seach will not find "ingm". How do I > implement in MYSQL/PHP a search that will have this action? please share the c

RE: fulltext search

> -Original Message- > - If you use one word in your search, 1 is a probable score, because all > the results that > appear have the same relevance (they all contain that word!). > - If you use two words, where the second isn't present in all results, you > shouldn't get > relevance value 1

RE: fulltext search

- If you use one word in your search, 1 is a probable score, because all the results that appear have the same relevance (they all contain that word!). - If you use two words, where the second isn't present in all results, you shouldn't get relevance value 1 in all results. - If you use the ex

RE: fulltext search

Try to delete 'in boolean mode' Santino At 12:42 -0700 5-10-2004, Ed Lazor wrote: > -Original Message- Try this: select column1, match(column1) against ('+orange -fruit' IN BOOLEAN MODE) as score from some_table where match(column1) against('+orange -fruit' IN BOOLEAN MODE) order by

RE: fulltext search

> -Original Message- > Try this: > > select column1, match(column1) against ('+orange -fruit' IN BOOLEAN MODE) > as score > from some_table where match(column1) against('+orange -fruit' IN BOOLEAN > MODE) > order by score desc > > this way you have your results ordered by relevance, and y

Re: fulltext search

Try this: select column1, match(column1) against ('+orange -fruit' IN BOOLEAN MODE) as score from some_table where match(column1) against('+orange -fruit' IN BOOLEAN MODE) order by score desc this way you have your results ordered by relevance, and you also get the relevance value in the resul

Re: Fulltext Search takes 17 sec.

Wow, thanks Brent, nice to learn something new (I'm not much of a 'server' guy) Tried the iostat and got some results while performing a general query: mysql> SELECT count(*) FROM product_fulltext WHERE MATCH(search_text) AGAINST('DISK'); +--+ | count(*) | +--+ | 4975 | +--

Re: Fulltext Search takes 17 sec.

Grumble, grumble. I was hoping vmstat would tell us more. In a "nutshell", every system has a bottleneck and the bottleneck is always CPU, RAM, I/O or Network. Nutshells are great since they make things seem so simple. You've got a 1 in 4 chance sf picking the right piece that is your bottlenec

RE: Fulltext Search takes 17 sec.

Thanks for the vmstat tip. I ran vmstat 1 on the query on a slightly quicker query so I wouldn't have a ton of numbers to post from the vmstat. mysql> SELECT COUNT(*) FROM product_fulltext WHERE MATCH(search_text) AGAINST('Pink'); +--+ | COUNT(*) | +--+ |12231 | +--+ 1

Re: Fulltext Search takes 17 sec.

Those times shouldn't be that far apart. What is the hardware (RAM, CPU, etc.) and OS you are running this on? Is there anything else running on it that might be causing memory to page out? If you are running Unix, try running: vm_stat 1 That will show you memory stats every second. Watch the

Re: Fulltext Search takes 17 sec.

Thanks for all your help guys, Using COUNT(*) I get the following: mysql> SELECT COUNT(*) FROM product_fulltext WHERE MATCH(search_text) AGAINST('blue jeans'); +--+ | COUNT(*) | +--+ |51513 | +--+ 1 row in set (48.58 sec) The EXPLAIN for the fulltext queries look like

Re: Fulltext Search takes 17 sec.

If you really want to test the raw query speed, then do a SELECT COUNT(*). That will return just a count of the number of records found, eliminating any speed issues caused by display processing or transfer speeds from the database to the interface. Adding a limit usually speeds things up since

RE: Fulltext Search takes 17 sec.

Hi Brent, Oops, sorry about forgetting to post the key buffer size, its: > key_buffer_size 262144000 As far as the "combined column" I'm using, I did it to make the fulltext as simple as possible and keep the index at only 1 column. I am aware that I can create an index for multiple columns but

RE: Fulltext Search takes 17 sec.

On your two word plus searches, `New York` for example, have you tried using `IN BOOLEAN MODE` to reduce the number of false positives? AGAINST("New York" IN BOOLEAN MODE) -Original Message- From: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: 8/12/04 8:33 AM Subject: RE: Fullt

RE: Fulltext Search takes 17 sec.

Hi Victor, The fulltext index was created on 1 column only that is of type "text". The benchmarks I get are very inconsistant... SELECT product_id FROM product_fulltext WHERE MATCH ( search_text ) AGAINST ('China') >Query took 20.17 seconds SELECT product_id FROM product_fulltext WHERE MATCH

Re: Fulltext Search takes 17 sec.

Missed your original message. What do you mean you concatenated the columns you wanted to search on and placed them in a table? You should just create the full text index on multiple columns. For instance, in a contacts table, you may have firstname, lastname. So you would create a full text in

RE: Fulltext Search takes 17 sec.

: Fulltext Search takes 17 sec. Hmmm... looks like it may be impossible to do fulltext searching on 3 million rows as few have chimed in on this one. Just to add some background to my setup, I am currently running on MySQL 4.0.17 (plan to upgrade soon.. will this help??) and I created the index that took

RE: Fulltext Search takes 17 sec.

Hmmm... looks like it may be impossible to do fulltext searching on 3 million rows as few have chimed in on this one. Just to add some background to my setup, I am currently running on MySQL 4.0.17 (plan to upgrade soon.. will this help??) and I created the index that took 9 minutes to process

Re: FULLTEXT search

Match() can be called 'In Boolean Mode' if you wish. See the docs at http://dev.mysql.com/doc/mysql/en/Fulltext_Search.html. PB - Original Message - From: Schalk Neethling To: [EMAIL PROTECTED] Sent: Thursday, July 22, 2004 9:17 AM Subject: FULLTEXT search When doing a MATCH(

Re: FULLTEXT search

"OR" From the manual: "Every correct word in the collection and in the query is weighted according to its significance in the collection or query." http://dev.mysql.com/doc/mysql/en/Fulltext_Search.html If you want "AND", look at the boolean full-text searches format: http://dev.mysql.com/doc/mys

Re: Fulltext search over multiple tables

I think you want a UNION, not a JOIN. Availabilty of UNION depends on the version you are running. Remi Mikalsen wrote: Hello. I have a problem I believe must have been solved lots of times before. I am doing a fulltext search on two tables at the same time. The problem is that it takes about 20

Re: FULLTEXT search in form of MATCH...AGAINST

Robb Kerr <[EMAIL PROTECTED]> wrote: > I can't seem to get a FULLTEXT search in the form of MATCH...AGAINST to > work. I even copied verbatim the example listed on mysql.com at > (http://www.mysql.com/doc/en/Fulltext_Search.html). When I use... > > SELECT * FROM articles WHERE MATCH (title,body) A

Re: FULLTEXT search in form of MATCH...AGAINST

Hello Robb, Thursday, April 8, 2004, 4:30:46 PM, you wrote: RK> I've got several tables with FULLTEXT indexes and on none of them can I get RK> this syntax to work. What's up? Your version of MySQL perhaps? -- Best regards, Richard Davey http://www.phpcommunity.org/wiki/296.html -- MySQL

Re: Fulltext search question: words with numbers (ie DB2)

Brent Baisley wrote: Not as far as I know. Boolean forces all matches to have all the words searched on, rather than relevance ranking the results based on how many of the specified search words are in a record. Searching in boolean mode will always return the same or less results than a regula

Re: Fulltext search question: words with numbers (ie DB2)

Not as far as I know. Boolean forces all matches to have all the words searched on, rather than relevance ranking the results based on how many of the specified search words are in a record. Searching in boolean mode will always return the same or less results than a regular full text search.

Re: Fulltext search question: words with numbers (ie DB2)

Brent Baisley wrote: The other thing to consider is the 50% rule. If more than 50% of the records match, the search is consider irrelevant and no records are returned. So if you have 120 records and 61 have DB2 in them, you won't get a result set. But the 50% rule is overridden when the search

Re: Fulltext search question: words with numbers (ie DB2)

The other thing to consider is the 50% rule. If more than 50% of the records match, the search is consider irrelevant and no records are returned. So if you have 120 records and 61 have DB2 in them, you won't get a result set. On Mar 31, 2004, at 12:28 AM, Shane Allen wrote: apologies, I forgo

Re: Fulltext search question: words with numbers (ie DB2)

Richard Davey wrote: Hello Shane, Wednesday, March 31, 2004, 5:43:10 AM, you wrote: SA> using MATCH(description) AGAINST('+db2' IN BOOLEAN MODE) returns no results. SA> Is this expected behaviour? If so, is there a way to circumvent it? By default, the full text indexing engine doesn't include w

Re: Fulltext search question: words with numbers (ie DB2)

Hello Shane, Wednesday, March 31, 2004, 5:43:10 AM, you wrote: SA> using MATCH(description) AGAINST('+db2' IN BOOLEAN MODE) returns no results. SA> Is this expected behaviour? If so, is there a way to circumvent it? By default, the full text indexing engine doesn't include words with less than 4

Re: fulltext search always returns no results

"Don Dikunetsis" <[EMAIL PROTECTED]> wrote: > > Hi, > > The comments in the fulltext doc page > (http://www.mysql.com/doc/en/Fulltext_Search.html) discuss the issues of > stopwords and over 50% hits, so I did my best to avoid those particular > bombs in my searches. > > The "subject" column c

Re: fulltext search always returns no results

actually contains anything? From: "Matt W" <[EMAIL PROTECTED]> To: "Don Dikunetsis" <[EMAIL PROTECTED]>, <[EMAIL PROTECTED]> Subject: Re: fulltext search always returns no results Date: Thu, 26 Feb 2004 01:26:17 -0600 Hi Don, No, full-text search was added

RE: fulltext search always returns no results

arches still return blank results. I must admit that at this point I'm stumped! From: "Peter Lovatt" <[EMAIL PROTECTED]> To: "Matt W" <[EMAIL PROTECTED]>, "Don Dikunetsis" <[EMAIL PROTECTED]>, <[EMAIL PROTECTED]> Subject: RE: fulltext se

Re: fulltext search always returns no results

> Hi Don, > > No, full-text search was added in MySQL 3.23.23, I believe (4.0.1 just > added boolean searches along with more speed overall). It doesn't need > to be compiled in or anything, it's there by default. Unless someone > compiled it and actually *removed* the full-text code or something

Re: fulltext search always returns no results

riginal Message - From: "Don Dikunetsis" Sent: Thursday, February 26, 2004 12:21 AM Subject: Re: fulltext search always returns no results > > Hi, thanks for your reply, but it looks like: > > > As of Version 3.23.23, MySQL has support for full-text indexing and &

Re: fulltext search always returns no results

k with your configuration"--my > setup certainly doesn't seem to be responding to the normal setup > instructions for fulltext search. > > >>From: <[EMAIL PROTECTED]> >>To: <[EMAIL PROTECTED]> >>CC: <[EMAIL PROTECTED]> >>Subject: R

Re: fulltext search always returns no results

of "this won't work with your configuration"--my setup certainly doesn't seem to be responding to the normal setup instructions for fulltext search. From: <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> CC: <[EMAIL PROTECTED]> Subject: Re: fulltext search always

Re: fulltext search always returns no results

Excuse if i'm not correct but this may be your problemo ? MySQL 3.23.55 running on my webhost's Linux box phpMyAdmin 2.1.0 I didnt think fulltext was in 3.23 wasnt this a Mysql 4 feature ?? > Summary: When I run a fulltext search, it always returns no results. I > have added a fulltext index

Re: Fulltext search

"Santino" <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED] > Is it possible to create a InnoDB table and a MyIsam table with > fulltext indexes and use a join to search in fulltext indexes? > Santino > Yup.. you can.. create the tables on the same DB and make a JOIN.. -- MySQL Gene

Re: Fulltext search

Is it possible to create a InnoDB table and a MyIsam table with fulltext indexes and use a join to search in fulltext indexes? Santino At 18:43 -0600 23-01-2004, Paul DuBois wrote: At 18:34 -0600 1/23/04, Sidar LC. wrote: How can I implement fulltext search engine on InnoDB and MySQL 5. You can't

RE: Fulltext search

when when when will it be available for innodb ? -Original Message- From: Paul DuBois [mailto:[EMAIL PROTECTED] Sent: Saturday, January 24, 2004 11:43 AM To: Sidar LC.; [EMAIL PROTECTED] Subject: Re: Fulltext search At 18:34 -0600 1/23/04, Sidar LC. wrote: >How can I implement fullt

Re: Fulltext search

At 18:34 -0600 1/23/04, Sidar LC. wrote: How can I implement fulltext search engine on InnoDB and MySQL 5. You can't. FULLTEXT indexes are supported only for MyISAM tables. http://www.mysql.com/doc/en/Fulltext_Search.html -- Paul DuBois, MySQL Documentation Team Madison, Wisconsin, USA MySQL AB,

Re: FULLTEXT Search and Hyphens

Michael, have a look at the sources, especially myisam/ft_parser.c near line 108 and at myisam/ftdefs.h. It should not be difficult to hack the sources to make the hyphen a real character. This will solve your problem (but could create some new ones on others types of text input). Thomas On Wed

Re: FULLTEXT Search and Hyphens

Sorry about this, > The only way to search for kk-4835 is to do the > search > in Boolean mode and put things in quotes -> > "kk-4835" > So your query would look like this: > > > SELECT * FROM ms_items > > where MATCH (it_mnfgID, it_title, it_descrip) > > AGAINST ('"kk-4835"' IN BOOLEAN MODE ) P

Re: FULLTEXT Search and Hyphens

Hello, Fulltext section of mysql manual: "MySQL uses a very simple parser to split text into words. A "word" is any sequence of characters consisting of letters, digits, " ' ", and " _ ". Any "word" that is present in the stopword list or is just too short is ignored." Thus a hyphen would be vi

Re: FULLTEXT Search and Hyphens

In the last episode (Dec 31), michael elston said: > I am having some trouble with fulltext search when searching a Table > for parts numbers which contain HYPHENS ( - ) and i am 90% sure that is > where the problem is. > > My query is: > SELECT * FROM ms_items > where MATCH (it_mnfgID, it_title

Re: fulltext search speed issue with SQL_CALC_FOUND_ROWS

Hello, > > Could one not store the total while using the > index > > and use "select FOUND_ROWS()" without > > SQL_CALC_FOUND_ROWS to retrieve the total? > > Yes, it could. > It is the optimization that wasn't implemented yet. > (but it's in the TODO) Once again, thanks for the response. Could

Re: fulltext search speed issue with SQL_CALC_FOUND_ROWS

Hi! On Dec 05, tk wrote: > Hello Sergei, Gunnar, and others, > > thank you for your quick responses. > One little mystery remains: > > Why does one need to read all the row data (with > SQL_CALC_FOUND_ROWS) to get the total number of > results when using a limit? > > When the index is used to

Re: fulltext search speed issue with SQL_CALC_FOUND_ROWS

Hello Sergei, Gunnar, and others, thank you for your quick responses. One little mystery remains: Why does one need to read all the row data (with SQL_CALC_FOUND_ROWS) to get the total number of results when using a limit? When the index is used to find relevant rows and sort the results, the c

RE: fulltext search speed issue with SQL_CALC_FOUND_ROWS

Hi TK, There was an optimizer bug in MySQL 4.0 This bug is fixed in 4.0.17 (not yet released) # Fixed bug when the optimiser did not # take SQL_CALC_FOUND_ROWS into account # if LIMIT clause was present. (Bug #1274) Kind regards Gunnar > -Original Message- > From: [EMAIL PROTECTED]

Re: fulltext search speed issue with SQL_CALC_FOUND_ROWS

Hi! On Dec 04, tk wrote: > Hello, > > Thanks for the response. > There is one thing that is not clear however. > > Regardless of whether or not I perform the fulltext > search with or without the SQL_CALC_FOUND_ROWS > keyword, the results that I get are exactly the same. > > Also, the notion

Re: fulltext search speed issue with SQL_CALC_FOUND_ROWS

Hello, Thanks for the response. There is one thing that is not clear however. Regardless of whether or not I perform the fulltext search with or without the SQL_CALC_FOUND_ROWS keyword, the results that I get are exactly the same. Also, the notion of stopping after the limit is reached cannot

Re: fulltext search speed issue with SQL_CALC_FOUND_ROWS

Hi, Yes, you would have similar results with any query that uses SQL_CALC_FOUND_ROWS. That's because MySQL has to see how many rows would be found without the LIMIT. So in your case, it can't just abort the query after it finds 10 rows. All rows that match the WHERE need to be found. You might wa

Re: FullText search CJK in UTF-8

Hi! On Dec 02, Sergei Golubchik wrote: > Hi! > > On Dec 02, Hu, Yiguang wrote: > > Is the fulltext search working for cjk text (use UTF-8) in 4.1.0 alpha ? I > > have trouble doing search on cjk text in 4.1.0alpha, though it seems should > > be working according to the following doc: > > http://w

Re: FullText search CJK in UTF-8

Hi! On Dec 02, Hu, Yiguang wrote: > Is the fulltext search working for cjk text (use UTF-8) in 4.1.0 alpha ? I > have trouble doing search on cjk text in 4.1.0alpha, though it seems should > be working according to the following doc: > http://www.mysql.com/doc/en/Fulltext_Restrictions.html Nope.

Re: FullText search CJK in UTF-8

At 11:55 -0500 12/2/03, Hu, Yiguang wrote: Is the fulltext search working for cjk text (use UTF-8) in 4.1.0 alpha ? I have trouble doing search on cjk text in 4.1.0alpha, though it seems should be working according to the following doc: http://www.mysql.com/doc/en/Fulltext_Restrictions.html UTF-8 s

Re: FULLTEXT search oddity

Hi! On Sep 19, Michael Stassen wrote: > This doesn't surprise me. I haven't looked at the code, but I'd bet > that double-quoted, exact phrase matches are handled the usual way by > mysql: First, do a regular fulltext search (using the index) to find > rows with your search words, then check

Re: FULLTEXT search oddity

This doesn't surprise me. I haven't looked at the code, but I'd bet that double-quoted, exact phrase matches are handled the usual way by mysql: First, do a regular fulltext search (using the index) to find rows with your search words, then check the found rows to see if they exactly contain

RE: Fulltext search from multiple tables...

I have this strange feeling of deja-vu This was just posted to the list recently (last week?), and currently, you cannot do cross-table full-text indexes, excepting boolean text searches, which would be slow. I have this strange feeling of deja-vu Dan Greene > -Original Message-

Re: FULLTEXT search

At 10:09 PM 9/5/2003, Chris Nolan wrote: Mike, What a brilliant idea! Seriously, setting up a community fund to sponsor this (and perhaps in future other things) might be something to consider. The only questions that come to mind are: 1. Which would be more effective, setting up a fund for this

Re: FULLTEXT search

Mike, What a brilliant idea! Seriously, setting up a community fund to sponsor this (and perhaps in future other things) might be something to consider. The only questions that come to mind are: 1. Which would be more effective, setting up a fund for this sort of thing or just going out and buyi

Re: FULLTEXT search

At 08:56 PM 9/4/2003, you wrote: Hi all, At the moment, we all know that InnoDB does not yet have FULLTEXT indexes. This is not another message asking as to when we will have that functionality. This message is different. On the mailing list for DBMail, we've been discussing MySQL table types, wit

Re: Fulltext search not returning matches..

At 9:25 -0400 7/30/03, Chad Day wrote: my query: SELECT * FROM `links` WHERE MATCH ( KEYWORDS ) AGAINST ( 'paper' ); I have a table with 4 records in it of links to various newspapers, paper and newspaper are both in the keywords field. The keywords field has a fulltext index on it. Did I tota

Re: Fulltext search not returning matches..

You didn't miss a step, everything is working as it should be. Meaning, MySQL will classify your search results as "irrelevant" if it matches more than half of the records. If you only have 4 records, chances are your search is matching at least two. Put a few more records in your database and

Re: FULLTEXT Search and Charsets

> > ... > >The FULLTEXT search only seems to find words in the latin charset. > > > >Does anyone have any guidance on how I can get it working with other > >charsets? > > FULLTEXT currently works only with single-byte character sets. And UTF-8 makes it easy to handle latin as if it were single-by

Re: FULLTEXT Search and Charsets

At 14:13 -0700 6/12/03, Peter Bryant wrote: Hi. I have a table with a fulltext search index on a field. I am inserting text using UTF-8 characters (with the JDBC driver). That includes words in English, French, Russian and Greek. The FULLTEXT search only seems to find words in the latin charset.

Re: Fulltext search -- no wildcards in phrases?

On Wed, 2 Apr 2003, Shamit Verma wrote: > The replay on the webpage says that: > "Nope. That would be a really slow search since mysql cant use any > indexes and a table scan would be the only way to find it." > > Then even "LIKE" operator should suffer from the same performance drawback, > how do

Re: Fulltext search -- no wildcards in phrases?

The replay on the webpage says that: "Nope. That would be a really slow search since mysql cant use any indexes and a table scan would be the only way to find it." Then even "LIKE" operator should suffer from the same performance drawback, how does LIKE operator work with indexes? Shamit Verma,

Re: fulltext search

Christian, While fulltext had some problems with latin1 charset and German language it worked quite well for me with latin1_de and a customized German stopword list. BTW I create my stopword list from the texts to be indexed. All words are sorted by frequency and then common words from the top of

re: Fulltext search -- no wildcards in phrases?

On Thursday 27 March 2003 20:59, Nick Arnett wrote: > It appears to me that fulltext phrase searches cannot include wildcards. > For example, I would expect "app* serv*" to match "application server," > "application services," etc. But it returns no results, so I'm having to > run each variation

Re: fulltext search

At 22:26 Uhr -0600 25.03.2003, mos wrote: How many people out there are willing to pay $$$ to see it done?? Please reply to this thread to see if there is a general interest and how much it is worth to you. IIRC, last time I looked, fulltext was not very good for i.e. the german language. If the

Re: fulltext search

At 09:03 PM 3/25/2003, you wrote: On Monday 24 March 2003 04:04 pm, Brian McCain wrote: > Maybe they should set up some way to donate via PayPal. I'm sure there are > plenty of developers around the world who'd be willing to chip in $10 here > or $20 there in order to be able to use fulltext search

Re: fulltext search

On Monday 24 March 2003 04:04 pm, Brian McCain wrote: > Maybe they should set up some way to donate via PayPal. I'm sure there are > plenty of developers around the world who'd be willing to chip in $10 here > or $20 there in order to be able to use fulltext searching on InnoDB > tables. > > I know

Re: fulltext search

On Mon, Mar 24, 2003 at 03:04:00PM -0800, Brian McCain wrote: > > Maybe they should set up some way to donate via PayPal. I'm sure > there are plenty of developers around the world who'd be willing to > chip in $10 here or $20 there in order to be able to use fulltext > searching on InnoDB tables.

Re: fulltext search

- From: "Jeremy Zawodny" <[EMAIL PROTECTED]> To: "Jennifer Goodie" <[EMAIL PROTECTED]> Cc: "Sidar Lopez Cruz" <[EMAIL PROTECTED]>; "MySQL" <[EMAIL PROTECTED]> Sent: Monday, March 24, 2003 2:44 PM Subject: Re: fulltext search > O

Re: fulltext search

On Mon, Mar 24, 2003 at 12:59:17PM -0800, Jennifer Goodie wrote: > You don't. > http://www.mysql.com/doc/en/Fulltext_Search.html > > There was a discussion on this mailing list last week or the week before on > when innoDB support would be implemented. I'm too lazy to look it up, you > should sea

RE: fulltext search

You don't. http://www.mysql.com/doc/en/Fulltext_Search.html There was a discussion on this mailing list last week or the week before on when innoDB support would be implemented. I'm too lazy to look it up, you should search the list archives for it. -Original Message- From: Sidar Lopez C

Re: fulltext search

Wynne, - Original Message - From: "Wynne Crisman" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Cc: "'Heikki Tuuri'" <[EMAIL PROTECTED]> Sent: Friday, March 21, 2003 5:18 AM Subject: Re: fulltext search > Since InnoDB tables don't s

Re: fulltext search

EMAIL PROTECTED] Subject: Re: fulltext search Sidar, > when MySQL will support fulltext search on InnoDB tables? we are still waiting for some customer to sponsor the porting. Best regards, Heikki Tuuri Innobase Oy --- InnoDB - transactions, hot backup, and foreign key support for MySQL

Re: fulltext search

Sidar, - Original Message - From: ""Sidar Lopez Cruz"" <[EMAIL PROTECTED]> Newsgroups: mailing.database.mysql Sent: Tuesday, March 18, 2003 10:50 PM Subject: fulltext search > > > > > when MySQL will support fulltext search on InnoDB tables? we are still waiting for some customer t

Re: Fulltext Search Problem

Hi Brian, Sorry, I was mistaken. It does work! The documents in question, were not category='sport'. Regards Martin "Brian McCain" <[EMAIL PROTECTED]> 18/03/2003 17:23 To: <[EMAIL PROTECTED]>, <[EMAIL PROTECTED]> cc:

  1   2   >