Re: mySQL 4 - FullText searching syntax?
Hi!
On Feb 07, Alain Fontaine - Consultant and developer wrote:
-- snip --
select
BienID
from
biens
where
MATCH(Notes) AGAINST('+appartemen* -lux* -prop*' IN BOOLEAN MODE)
-- snip --
This does not produce the correct result, whereas this does:
-- snip --
select
BienID
from
biens
where
MATCH(Notes) AGAINST('appartemen*' IN BOOLEAN MODE)
AND
NOT MATCH(Notes) AGAINST('lux*' IN BOOLEAN MODE)
AND
NOT MATCH(Notes) AGAINST('prop*' IN BOOLEAN MODE)
-- snip --
That looks like a bug, can you create a test case for it ?
Regards,
Sergei
--
MySQL Development Team
__ ___ ___ __
/ |/ /_ __/ __/ __ \/ / Sergei Golubchik [EMAIL PROTECTED]
/ /|_/ / // /\ \/ /_/ / /__ MySQL AB, http://www.mysql.com/
/_/ /_/\_, /___/\___\_\___/ Osnabrueck, Germany
___/
-
Before posting, please check:
http://www.mysql.com/manual.php (the manual)
http://lists.mysql.com/ (the list archive)
To request this thread, e-mail [EMAIL PROTECTED]
To unsubscribe, e-mail [EMAIL PROTECTED]
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
-
Before posting, please check:
http://www.mysql.com/manual.php (the manual)
http://lists.mysql.com/ (the list archive)
To request this thread, e-mail [EMAIL PROTECTED]
To unsubscribe, e-mail [EMAIL PROTECTED]
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
mySQL 4 - FullText searching syntax?
Hello,
I am evaluating mySQL 4.0.1-alpha on Redhat Linux 7.2 (RPM version). I am
playing with the new fulltext search features and I have a question
regarding the syntax...
I have created a fulltext index on a field 'Notes'. I'd like to search for
records that have words starting with appartemen in them, but NOT words
starting with lux, and neither with prop. So I thought this would do the
trick:
-- snip --
select
BienID
from
biens
where
MATCH(Notes) AGAINST('+appartemen* -lux* -prop*' IN BOOLEAN MODE)
-- snip --
This does not produce the correct result, whereas this does:
-- snip --
select
BienID
from
biens
where
MATCH(Notes) AGAINST('appartemen*' IN BOOLEAN MODE)
AND
NOT MATCH(Notes) AGAINST('lux*' IN BOOLEAN MODE)
AND
NOT MATCH(Notes) AGAINST('prop*' IN BOOLEAN MODE)
-- snip --
What have I understood wrong?
---
Alain Fontaine
Consultant Developer
VAlain S.A.
Tél: +32-4-2522950
---
-
Before posting, please check:
http://www.mysql.com/manual.php (the manual)
http://lists.mysql.com/ (the list archive)
To request this thread, e-mail [EMAIL PROTECTED]
To unsubscribe, e-mail [EMAIL PROTECTED]
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
-
Before posting, please check:
http://www.mysql.com/manual.php (the manual)
http://lists.mysql.com/ (the list archive)
To request this thread, e-mail [EMAIL PROTECTED]
To unsubscribe, e-mail [EMAIL PROTECTED]
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
mySQL 4 - FullText searching syntax?
Hello,
I am evaluating mySQL 4.0.1-alpha on Redhat Linux 7.2 (RPM version). I am
playing with the new fulltext search features and I have a question
regarding the syntax...
I have created a fulltext index on a field 'Notes'. I'd like to search for
records that have words starting with appartemen in them, but NOT words
starting with lux, and neither with prop. So I thought this would do the
trick:
-- snip --
select
BienID
from
biens
where
MATCH(Notes) AGAINST('+appartemen* -lux* -prop*' IN BOOLEAN MODE)
-- snip --
This does not produce the correct result, whereas this does:
-- snip --
select
BienID
from
biens
where
MATCH(Notes) AGAINST('appartemen*' IN BOOLEAN MODE)
AND
NOT MATCH(Notes) AGAINST('lux*' IN BOOLEAN MODE)
AND
NOT MATCH(Notes) AGAINST('prop*' IN BOOLEAN MODE)
-- snip --
What have I understood wrong?
---
Alain Fontaine
Consultant Developer
VAlain S.A.
Tél: +32-4-2522950
---
-
Before posting, please check:
http://www.mysql.com/manual.php (the manual)
http://lists.mysql.com/ (the list archive)
To request this thread, e-mail [EMAIL PROTECTED]
To unsubscribe, e-mail [EMAIL PROTECTED]
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
mysql and FULLTEXT
Hi there. I need to do this sentence: select * from table1 where match column1 against word; But it don´t works becouse crate the column like this: alter table table1 add column1 varchar(100); Well my question is: How I should create the column1 to have fulltext for this query?? Thanks Victor. - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
Re: mysql and FULLTEXT
On Wed, 2002-01-16 at 18:51, [EMAIL PROTECTED] wrote: Hi there. I need to do this sentence: select * from table1 where match column1 against word; Try: select * from table1 where match column1 against (word); But it don´t works becouse crate the column like this: alter table table1 add column1 varchar(100); That's ok, but don't forget to create an index of type FULLTEXT. (with ALTER TABLE or CREATE INDEX). There is a good example in: http://mysql.com/doc/F/u/Fulltext_Search.html Well my question is: How I should create the column1 to have fulltext for this query?? Thanks Victor. - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php -- Diana Soares - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
RE: mysql and FULLTEXT
I think you need to do this: ALTER TABLE table1 ADD FULLTEXT (column1) I may be wrong though, and I too have a question. Does adding the FULLTEXT index affect performance dramatically? If it does, what is a better way to search for exact word matches in columns that may contain thousands of words in each entry? LIKE doesn't do it properly. It will find 'then Richard said to' when I search for Rich and I don't want that.. Thanks, Rich Foreman -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Hi there. I need to do this sentence: select * from table1 where match column1 against word; But it don´t works becouse crate the column like this: alter table table1 add column1 varchar(100); Well my question is: How I should create the column1 to have fulltext for this query?? Thanks Victor. - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
mysql 4.0.0 fulltext stopwords and word weighting
Hi, Is there a way to prevent the 50% occurence threshold in mysql's fulltext search logic that causes words that appear in more than 50% of records to be considered stopwords? I have a table that has less than 1000 records and would like to do a fulltext search on two columns and have them returned in plain old 'nearest match' order, rather than 'weighted words based on occurences of the word' order. From the manual: Word MySQL is present in more than half of rows, and as such, is effectively treated as a stopword (that is, with semantical value zero). It is, really, the desired behavior - a natural language query should not return every second row in 1GB table. I don't desire this behaviour. I don't mind every second row in the table, as long as they're ordered by best match first, and no words are ignored, regardless of how frequently they appear. I saw mention of the 'boolean search' that seems to disregard the 50% threshold, but that's only in version 4.0.1 which isn't released yet, and I'm not sure if it will order by best match first. thanks for all your help, Mark. - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
Re: MySQL 4.0 fulltext search truncation bug?
Use % instead of *
cheers
--
sherzodR
On 26 Nov 2001, Harald Fuchs wrote:
According to the manual, section New Features of Full-text Search to
Appear in MySQL 4.0:
* `*' is a truncation operator.
The query
SELECT COUNT(*) FROM documents WHERE MATCH(txt) AGAINST ('Versailles')
returns 2, but
SELECT COUNT(*) FROM documents WHERE MATCH(txt) AGAINST ('Versaill*')
returns 0 on MySQL 4.0.
Is this a bug, or do I misunderstand the meaning of truncation?
-
Before posting, please check:
http://www.mysql.com/manual.php (the manual)
http://lists.mysql.com/ (the list archive)
To request this thread, e-mail [EMAIL PROTECTED]
To unsubscribe, e-mail [EMAIL PROTECTED]
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
-
Before posting, please check:
http://www.mysql.com/manual.php (the manual)
http://lists.mysql.com/ (the list archive)
To request this thread, e-mail [EMAIL PROTECTED]
To unsubscribe, e-mail [EMAIL PROTECTED]
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
Re: MySQL 4.0 fulltext search truncation bug?
Hi!
On Nov 26, sherzodR wrote:
Use % instead of *
cheers
--
sherzodR
On 26 Nov 2001, Harald Fuchs wrote:
According to the manual, section New Features of Full-text Search to
Appear in MySQL 4.0:
* `*' is a truncation operator.
The query
SELECT COUNT(*) FROM documents WHERE MATCH(txt) AGAINST ('Versailles')
returns 2, but
SELECT COUNT(*) FROM documents WHERE MATCH(txt) AGAINST ('Versaill*')
returns 0 on MySQL 4.0.
Is this a bug, or do I misunderstand the meaning of truncation?
First - no, according to the manual '*' is a truncation operator, not
'%', so your syntax is correct.
Second - probably it's a bug. I cannot say much as the code used by this
query was removed from MySQL source tree. It was replaced by completely
new boolean search engine written from scratch. Unfortunately it was
done several days _after_ 4.0.0 release.
Wait for 4.0.1 - it should be out in a few days.
Regards,
Sergei
--
MySQL Development Team
__ ___ ___ __
/ |/ /_ __/ __/ __ \/ / Sergei Golubchik [EMAIL PROTECTED]
/ /|_/ / // /\ \/ /_/ / /__ MySQL AB, http://www.mysql.com/
/_/ /_/\_, /___/\___\_\___/ Osnabrueck, Germany
___/
-
Before posting, please check:
http://www.mysql.com/manual.php (the manual)
http://lists.mysql.com/ (the list archive)
To request this thread, e-mail [EMAIL PROTECTED]
To unsubscribe, e-mail [EMAIL PROTECTED]
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
MySQL v4 FTS speed (Was: MySQL 4.0 fulltext search truncation bug?)
Second - probably it's a bug. I cannot say much as the code used by this query was removed from MySQL source tree. It was replaced by completely new boolean search engine written from scratch. Unfortunately it was done several days _after_ 4.0.0 release. Wait for 4.0.1 - it should be out in a few days. Question - how much (if any) performance improvement is to be expected from the new boolean search engine for FTS in 4.0.1? Regards. Gordan - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
Re: MySQL v4 FTS speed (Was: MySQL 4.0 fulltext search truncation bug?)
Sergei Golubchik wrote: Hi! I didn't test it yet. The one thing I can say just now that unlike natural language search code (as exists in MySQL in 3.23) it need not to build the complete list of matched documents in memory in advance. It means that with LIMIT it should be MUCH faster than the old code. Unfortunately, it also means that it does not auto-magically return documents with relevance decreased (without ORDER BY, that is). If I use ORDER BY relevance and LIMIT. Does it need to build the complete list of documents in memory in advance? Or will it just build enough to satisfy the limit constraints. Regards, Sergei - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
MySQL 4.0 FULLTEXT SPEED
Hi Everyone, I've compiled the mysql 4.0 version on my computer to test the speed of creating full text indexes. I read that it was supposed to be 100 x faster than 3.23. However, it seems just as slow to me. I've been building an index on my 400+MB table for 5 days now. Does anyone have any experience with 4.0 to know how the FULLTEXT indexing is working. Would you say that it's much faster than 3.23? P - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
RE: MySQL 4.0 FULLTEXT SPEED
correct me if I'm mistaken, but I believe the latest version of mysql is 3.23.38 -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of [EMAIL PROTECTED] Sent: Tuesday, May 15, 2001 1:04 PM To: [EMAIL PROTECTED] Subject: MySQL 4.0 FULLTEXT SPEED Hi Everyone, I've compiled the mysql 4.0 version on my computer to test the speed of creating full text indexes. I read that it was supposed to be 100 x faster than 3.23. However, it seems just as slow to me. I've been building an index on my 400+MB table for 5 days now. Does anyone have any experience with 4.0 to know how the FULLTEXT indexing is working. Would you say that it's much faster than 3.23? P - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
Re: MySQL 4.0 FULLTEXT SPEED
On Tue, May 15, 2001 at 02:06:32PM -0400, Dave Carter wrote: correct me if I'm mistaken, but I believe the latest version of mysql is 3.23.38 That's the released version, yes. But you can pull a source copy of the MySQL 4.0 tree and compile it yourself if you're in the mood for some fun. :-) Jeremy -- Jeremy D. Zawodny, [EMAIL PROTECTED] Technical Yahoo - Yahoo Finance Desk: (408) 349-7878Fax: (408) 349-5454Cell: (408) 439-9951 MySQL 3.23.29: up 132 days, processed 818,902,134 queries (71/sec. avg) - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
