MyHits_HitKeeper Query Hub Result Help Database _
4 Full-text Searches

4.1 Purpose

The full-text search capability of HitKeeper allows to search the description of an entry for matching parts, i.e. in the text that is returned by the [seq|mot|cla]_[fetch|dump]_desc methods.

 

4.2 Syntax

The search is performed in case-insensitive fashion.

Every word is “in principle” optional in the query. The following qualifiers are supported to alter this behaviour:

+
a leading plus sign indicates that the word must be present (Beware that the ’+’ character in an URL is translated into a space. Use ’%2B’ if you really want to mean ’plus’ in an URL).
-
a leading minus sign indicates that the word must not be present (The - operator acts only to exclude rows that are otherwise matched by other search terms. Thus, a search that contains only terms preceded by - returns an empty result. It does not return all rows except those containing any of the excluded terms).
~
same effect as ’-’ above.
"..."
a phrase that is enclosed within double quotes must be present as it was typed (this is one of the rare cases were quotes are employed in the HitKeeper user interface!)
*
the asterisk serves as the truncation, or wildcard operator. Unlike the other operators, it must be appended to the word to be affected.
%
same effect as ’*’ above.

There are both obvious and obscure differences the between the MySQL and Oracle implementations of full-text search:

  • The scoring scheme is different.
  • Characters distinct from letter and digits may be interpreted differently, as it is the case with ’_’.

Please refer to the respective user manuals for further informations.

Question or comment about this page.