Release 1.3 - ...

<query> element

The query element defines the (main) search query for a particular source. It usually contains multiple local instance viper calls to be able to resolve certain parts of the query dynamically.

For instance, when the enclosing searchbase element contains an weights element (defining various weight factors) and there have been two specific physical field-weights configured (e.g. title and description), the value of the query element will be resolved three times.

The first time the {this.isbasequery()} viper will resolve to true and the {this.fieldname()} will resolve to its specified default (which should be "QueryData, CTSpecificBinary1"). The {this.fieldweight()} will resolve to a sql statement which uses the dbo.fn_AgeInDays() function to apply the age factor.

However, the second and third time, the {this.fieldname()} and {this.fieldweight()} viper calls will resolve in the fieldname (in this case title and description respectively) and the weight factor for that specific field (the specified default).

These three queries are then combined (using UNION ALL) and will then be used as search query for this particular source. This way you can assign more weight for specific fields.

Expand image Example

Expand image Attributes

Expand image Parent element

Expand image Child elements

Expand image Local Vipers