Quell supports search expressions:
windows
like windows
windows and driver and not video
windows near driver or "sound card"
(window* and driver) or (sound and card?)
like, near
not
and, or
The syntax for these operators is
like <string>
<string> near <string>
not <expression>
<expression> or <expression>
<expression> and <expression>
where <string> is a string with or without a wildcard (e.g. windows, window*), <expression> is a <string>, another operator, or parentheses enclosing an expression.
Like searches find words that match or nearly match those words entered in the query. Currently no working very good since the soundex function is for german. We are working on an English function.
Quell 4 supports wildcard searches in all operations. A search for ‘person* and comput*’ would find locations that contain an instance of both ‘person*’ and ‘comput*’. On the results page you will find the first 50 found words. Just click on them to start a new search.
? ... stands for one character
* ...stands for a number of characters
Searching for phrases or searching for one word near another word is a proximity search. In order to keep the size of the word indexes to a minimum, Quell does not store proximity information. As a result, when a proximity search is performed, Quell first narrows the list of possible locations using an
"AND" search, and then reads the text of the eligible locations to determine whether they meet the search criteria.
Appearing below are some common mistakes:
Mistake |
Solution |
| (windows or driver) near video | Windows near video or driver near video |
| like (problem or corruption) | Like problem or like corruption |
| like 'delphi' | Like delphi |
| like "borland delphi" | None |
| windows or driver not video | Windows or driver and not video |
| windows driver | Windows and driver |
Other common errors include not matching quotes (which may be paired single or double
quotes) or parenthesis.
The following expressions are equivalent:
| windows and driver near video | windows and (driver near video) |
| windows or driver and not video | (windows or driver) and not video |
| windows and driver and video | ((windows and driver) and video) |
The expression evaluator does not attempt to optimize the expression. This only becomes significant with searches using NEAR or phrases because these searches require reading the Text.
(parts out of Rubicon manual)