Table of Contents

Search

  1. Preface
  2. Introduction
  3. Defining a System
  4. Flattening IDTs
  5. Link Tables
  6. Loading a System
  7. Static Clustering
  8. Simple Search
  9. Search Performance
  10. Miscellaneous Issues
  11. Limitations
  12. Error Messages

Simple Search Definition

Simple Search Definition

You can define a simple search with a regular search definition in a system definition file.
Use the SDF Wizard to create a simple search definition. However, you can also create a definition outside the SDF Wizard subject to the rules for each of the components in the system definition file.
Index Definition
You can use any index that uses the indexing algorithm
Generic_Field
as Generic index. Normally, generic indexes include all columns that need to be searchable using simple search. A column in a Generic index must share a common IDT datatype.
Search Definition
Any search based on a generic index can potentially behave as a simple search. The limit on number of characters that make up a search name is reduced by three for simple searches.
Search Logic
Search fields that make up the simple search must contain all fields used by the associated generic index. Only the
Generic_Field
algorithm may be used in search logic of a simple search. The CONTROLS must specify a combine option for all search fields with no delimiters between them.
For example,
Controls ("FIELD=Generic_Field SEARCH_LEVEL=Typical COMBINE=Generic_Field:DELIM-NONE")
Score Logic
Score fields that make up the simple search must contain all fields that the associated generic index uses. You can use only the
Generic
purpose in score logic of a simple search. The CONTROLS must specify a combine option for all search fields with no delimiters between them.
For example, Controls
("FIELD=Generic_Field SEARCH_LEVEL=Typical COMBINE=Generic_Field:DELIM-NONE")
The match fields must be of type
Generic_Field
.
For example,
Matching-Fields ("FNAME:Generic_Field,LNAME:Generic_Field,ORG:Generic_Field,ADDR:Generic_Field")
Processing View
Simple search requires a special view definition that is used for search input processing. The processing view must have a name that contains the search name and the suffix
-GP
.
For example, if the search name is
my_search1
, the view name must be
my_searcg1-GP
The processing view must contain all fields required to assemble the simple search.
Display View
Simple search requires a special view definition that is used for search fields display. The display view must have a name with the characters
-GD
as a suffix to search name.
For example, if the search name is
my_search1
, the view name must be
my_searcg1-GD
.
The display view must contain a single field of size that is the total size of fields used in the processing view. The name of the field must not be an existing IDT column. The field name chosen for display view appears as a field when viewed through search clients. When using API
search_search_layout
, the name of field appears as a search column in the search layout.
To construct search input, it may be necessary to get attributes such as lengths and offsets of search columns. Such details should be obtained using
search_search_layout
. In case of simple search, the search fields will not be a part of the IDT and therefore IDT layout should not be used to determine lengths and offsets.

Back to Top

0 COMMENTS

We’d like to hear from you!