toooo deep. rubarb

Repllly Rubarb3

reply #2 Rubarb 3

It is spelt rhubarb

This is so silly!

I heard that too.

well no wonder it wasn't coming up in search.

Actually.. I intentionally misspell foods I hate.

Back on topic though.. can anyone shed some light on whether or not any wild card, inclusion, exclusion or grouping symbols are available during advanced search? ex: * + - "" If not available.. these would be extremely useful, and much appreciated if they were added.

+ - and " are all possible as it's just using MySQL's fulltext boolean search mode. Wildcard I'd need to look up and then make sure it's working properly.

Saaaweeet. Thanky. More testing. rubarb rubarb rhubarb...

Paul, could you provide a few sample searches for testing?

From http://www.phpfreaks.com/tutorials/129/0.php

Booean Full-Text Search Mode Operators

(From the MySQL Manual)

None
By default (when neither + nor - is specified) the word is optional, but the rows that contain it are rated higher. This mimics the behavior of MATCH() ... AGAINST() without the IN BOOLEAN MODE modifier.

+
A leading plus sign indicates that this word must be present in every row returned.

-
A leading minus sign indicates that this word must not be present in any row returned.

> <
These two operators are used to change a word's contribution to the relevance value that is assigned to a row. The > operator increases the contribution and the < operator decreases it. See the example below.

( )
Parentheses are used to group words into subexpressions. Parenthesized groups can be nested.

~
A leading tilde acts as a negation operator, causing the word's contribution to the row relevance to be negative. It's useful for marking noise words. A row that contains such a word is rated lower than others, but is not excluded altogether, as it would be with the - operator.

"
A phrase that is enclosed within double quote ('"') characters matches only rows that contain the phrase literally, as it was typed. The full-text engine splits the phrase into words, performs a search in the FULLTEXT index for the words. Before MySQL 5.0.3, the engine then performs a substring search for the phrase in the records that are found, so the match must include non-word characters in the phrase. As of MySQL 5.0.3, non-word characters need not be matched exactly: Phrase searching requires only that matches contain exactly the same words as the phrase and in the same order. For example, "test phrase" matches "test, phrase" as of MySQL 5.0.3, but not before.



Booelan Full-Text Search Examples

(From the MySQL Manual)

apple banana Find rows that contain at least one of the two words.

+apple +juice Find rows that contain both words.

+apple macintosh Find rows that contain the word ``apple'', but rank rows higher if they also contain ``macintosh''.

+apple -macintosh Find rows that contain the word ``apple'' but not ``macintosh''.

+apple +(>turnover <strudel) Find rows that contain the words ``apple'' and ``turnover'', or ``apple'' and ``strudel'' (in any order), but rank ``apple turnover'' higher than ``apple strudel''.

apple* Find rows that contain words such as ``apple'', ``apples'', ``applesauce'', or ``applet''.

"some words" Find rows that contain the exact phrase ``some words'' (for example, rows that contain ``some words of wisdom'' but not ``some noise words''). Note that the '"' characters that surround the phrase are operator characters that delimit the phrase. They are not the quotes that surround the search string itself.

In addition to my initial "rubarb" test above, I've been using a combination of the following words to test the advanced search operators listed above:

Calendar
Public
Private
Calendrical
Publication
Privatization

The last three words were used to test the * wildcard. They appear in one post (well, now two posts including this one). The wildcard doesn't appear to be working at the moment. A search for Calend*, Public* or Privat* does not return hits on those words.

There are some other strange things going on with the other operators. Not sure the <, >, (, ), or ~ operators are functional here. I haven't been able to come up with a search pattern that works for these.

Exact Phrase "" operator works.

+ and - operators sometimes work, sometimes do not work, depending on how they are applied (still trying to figure out the patterns)

Rick, let me know if I'm on the right track here. If these operators are not the set you incorporated, I'll stop trying to find the quirks with them.

After additional testing I've come up with the following:

• * wildcard does not work
• Highlighted search results (bold italic) are only present if the operators are not used
• Grouping "", Include +, Exclude - all work ok, except as noted above, the result hits are not highlighted in bold italic
• Nested combinations of searches (ex.: multiple +, multiple "", multiple no-operators) all work fine.
• (,),<,> and ~ operators do not work
• Search results are always sorted by date, most recent first. The sort modifiers above are not active.

Rick, have you had a chance to confirm these boolean functions?

Thanks

Looks good