Tamino XQuery User Guide - Software AG Documentation

Text Retrieval
declare namespace ino="http://namespaces.softwareag.com/tamino/response2"
for $p in collection("ino:vocabulary")/ino:term
where tf:containsText($p/ino:termName,tf:broaderTerms("dog"))
return $p/ino:termName
Here, the two ino:termName instances for dog and carnivore are returned.
Pattern Matching
You can conveniently perform text searches with the help of search patterns. Tamino's text retrieval
system allows for efficient queries using special characters that match one or more characters in
a word. In Tamino XQuery the following functions support text search using pattern matching:
tf:containsText
tf:containsAdjacentText
tf:containsNearText
tf:createTextReference
tf:createAdjacentTextReference
tf:createNearTextReference
The tokenizer that is being used determines the pattern matching facilities that are available. The
following table gives an overview of the characters that have a special meaning when used in one
of the above functions:
Character
Tokenizer Availability
Effect
? (maskcard)
white space-separated match a single character in a word
* (wildcard) CJK
white space-separated
match zero or more characters in a word
\ (escapecard) white space-separated cancel the special meaning of the following character
The default tokenizer ("white space-separated") supports all types of special characters, whereas
the Japanese tokenizer only supports wildcard characters. The section Wildcard Characters
provides details about the peculiarities when using the Japanese tokenizer.
The table above shows the default settings. However, with the white space-separated tokenizer
you can use a different character for each of these special characters. If, for example, your data
frequently uses the asterisk sign as a regular character, it is more convenient to redefine the
wildcard character instead of having to escape the asterisks using the escapecard character every
time they occur. See the section Customizing Special Character Settings for information on how
to change these settings. The discussion here assumes the default settings as defined in
ino:transliteration and, if not stated otherwise, the usage of the standard white space-separated
tokenizer.
98
XQuery User Guide