Understanding Search: value queries
27 October 2017 11:01 AM
Here we summarize some characteristics of value queries and compare to other approaches.
Punctuation and space tokens are not indexed as words in the universal index. Therefore, word-queries involving whitespace or punctuation will not make use of whitespace or punctuation in index resolution, regardless of space or punctuation sensitivity.
Punctuation and space tokens are also not generally indexed as words in the universal index in value queries either. However, as a special exception there are terms in the universal index for "exact" value queries ("exact" is shorthand for "case-sensitive", "diacritic-sensitive", "punctuation-sensitive", "whitespace-sensitive", "unstemmed", and "unwildcarded"). "exact" value queries should be resolvable properly from the index, but only if you have fast-case-sensitive-searches and fast-diacritic-sensitive-searches enabled in the database.
For field-word or field-value queries you can modify what counts as punctuation or whitespace via tokenizer overrides. This can turn what would have been a phrase into a single word.
Outside of the special case given for exact value queries, all queries involving space or punctuation are phrase queries. Word and value search is not string matching.
Space insensitive and punctuation insensitive do not mean tokenization insensitive. "foo-bar" will not match "foobar" as a value query or a word query, regardless of your punctuation sensitivity. Word and value search is not string matching.
Stemming is handled differently between a word-query and value-query; a value-query only indexes using basic stemming.
String range queries are about string matching. Whether there is a match depends on the collation, but there is no tokenization and no stemming happening.
If you want to do exact queries you can
As with all queries,
For example, the plan for