%iFind.Index.Minimal
index class %iFind.Index.Minimal extends %Library.FunctionalIndex, %Compiler.Type.Embedded
This class offers a subset of the full-text search capabilities brought by %iFind.Index.Basic with a minimal storage footprint. The following Basic features are not available for a Minimal index:
- Positional search: e.g. "[five tickets]", "[aspirin ? daily]
- Cooccurence search: e.g. "[ketchup, mayonaise, 5]"
- Highlighting search results
- Ranking search results
See the class reference of %iFind.Index.Basic for a detailed overview of available search capabilities.
Method Inventory
- DeleteIndex()
- Embedded()
- Find()
- InsertIndex()
- Normalize()
- PurgeIndex()
- SortBeginIndex()
- SortEndIndex()
- UpdateIndex()
Parameters
When generating SQL projections of iFind index data using the IFINDMAPPINGS), this parameter overrides the naming of those classes, using this parameter's value instead of the default [class_name]_[index_name] prefix. The projections will still be created in the [package_name]_[class_name] package.
When this parameter is set to 1, additional SQL projections will be created upon compiling the class. These are accessible as read-only tables in a package named [package_name]_[class_name] and have names starting with [class_name]_[index_name] (which can be overridden through IFINDADVANCEDSQLPREFIX).
By default, the following mappings are generated for an %iFind.Index.Minimal index:
- [class_name]_[index_name]_WordRec: stores which words appear in each record in this index. See also %iFind.Index.AbstractWordRec.
Additional classes will be generated automatically, based on your index class and parameters. See the class reference for subclasses for more details.
This parameter controls whether leading and trailing punctuation is ignored in its entirety or not for this index and associated searches. If set to 0, the index will also track words with adjacent punctuation to enable specifically searching for those occurrences.
- 0 = Do not store compounds or stems
- 1 = Store word-level stems
- 2 = Store word-level compounds and stems
See also %iKnow.Stemmer and %iKnow.Stemming.DecompoundUtils for more details on stemming or decompounding, or TRANSFORMATIONSPEC for advanced options to use custom transformations.
This parameter can be used to override the default stemming implementation when INDEXOPTION > 0. To do so, set this parameter to a saved %iKnow.Stemming.Configuration instance. This parameter has no effect if INDEXOPTION = 0.
This parameter is for advanced use only and empty by default.
This parameter defines the word transformation(s) to apply to input text, such as stemming, decompounding
and other operations for "normalizing" words, so searches can scan these normalized forms rather
than the literal forms.
This parameter cannot be set in conjunction with the INDEXOPTION
and/or STEMMINGCONFIG parameters, which are shorthands for configuring stemming
and decompounding options and overriding the default configurations for those.
This parameter also allows using custom transformations by specifying the name of a class that
inherits from %iFind.Transformation.Abstract, optionally followed by a colon and
string that will be passed onto the Transform method of the transformation class if it accepts
any parameters.
This parameter controls which user dictionary should be used to rewrite or annotate text before it is processed by the NLP engine. See NLP User Dictionaries in the NLP documentation.
This parameter is for advanced use only and empty by default.
Methods
SELECT * FROM MyPackage.Table WHERE %ID %FIND search_index(<i>index_name</i>, <var>pSearch</var> [, <var>pOption</var> [, <var>pLanguage</var>]])