[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
Given a search string of 'NA&SD' my default Fulltext search doesn't find
it. Wondered why? Is there a fix? Thanks for the help.
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Given a search string of 'NA&SD' my default Fulltext search doesn't find
it. Wondered why? Is there a fix? Thanks for the help.
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
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
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.
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
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
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
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
I have a table with the following:
CREATE TABLE foo (
...
description text,
...
FULLTEXT INDEX (description),
...
);
select count(*) from foo where description like '%db2%';
returns 61 rows. Checking them confirms that the "word" db2 exists as a
standalone word separated either by punctuation or
Hi!
On Oct 25, Lowell Allen wrote:
> Thanks for the reply, Sergei. I think I've since found the problem in the
> MySQL documentation -- under "Fulltext restrictions", 6.8.1, "All parameters
> to the MATCH function must be columns from the same table that is part of
> the same fulltext index." I n
Hi!
On Oct 24, Lowell Allen wrote:
> I'm trying to do a search against two fulltext indexes. I can successfully
> search against either one separately, like:
>
> $psl->set_query("SELECT Products.ID, Products.Name, " .
> "Products.Photo, Products.Description " .
> "FROM Products, Cate
I'm trying to do a search against two fulltext indexes. I can successfully
search against either one separately, like:
$psl->set_query("SELECT Products.ID, Products.Name, " .
"Products.Photo, Products.Description " .
"FROM Products, Categories, ProductsCategories " .
"WHERE Catego
13 matches
Mail list logo
