542
Chapter 25: Using Verity Search Expressions
You can use paired backquotes or backslashes to escape special characters. There is no functional
difference between the two. For example, you can query for the term: <DDA> using
\<DDA\>
or
`<DDA>`
as your search term.
Composing search expressions
The following rules apply to the composition of search expressions.
Case sensitivity
Verity searches are case-sensitive only when the search term is entered in mixed case. For example,
a search for zeus finds zeus, Zeus, or ZEUS; however, a search for Zeus finds only Zeus.
To have your application always ignore the case the user types, use the
LCase
function in the
criteria
attribute of
cfsearch
. The following code converts user input to lowercase, thereby
eliminating case-sensitivity concerns:
<cfsearch name="results"
collection="#form.collname#"
criteria="#LCase(form.criteria)#"
type="#form.type#">
Prefix and infix notation
By default, Verity uses
infix notation
, in which precedence is implicit in the expression; for
example, the AND operator takes precedence over the OR operator.
You can use
prefix notation
with any operator except an evidence operator (typically, STEM,
WILDCARD, or WORD; for a description of evidence operators, see
“Evidence operators”
on page 548
). In prefix notation, the expression explicitly specifies precedence. Rather than
repeating an operator, you can use prefix notation to list the operator once and list the search
targets in parentheses. For example, the following expressions are equivalent:
•
Moses <NEAR> Larry <NEAR> Jerome <NEAR> Daniel <NEAR> Jacob
•
<NEAR>(Moses,Larry,Jerome,Daniel,Jacob)
The following prefix notation example searches first for documents that contain Larry and
Jerome, then for documents that contain Moses:
OR (Moses, AND (Larry,Jerome))
The infix notation equivalent of this is as follows:
Moses OR (Larry AND Jerome)
Commas in expressions
If an expression includes two or more search terms within parentheses, a comma is required
between the elements (whitespace is ignored). The following example searches for documents that
contain any combination of Larry and Jerome together:
AND (Larry, Jerome)
Summary of Contents for COLDFUSION MX 61-DEVELOPING COLDFUSION MX
Page 1: ...Developing ColdFusion MX Applications...
Page 22: ...22 Contents...
Page 38: ......
Page 52: ...52 Chapter 2 Elements of CFML...
Page 162: ......
Page 218: ...218 Chapter 10 Writing and Calling User Defined Functions...
Page 250: ...250 Chapter 11 Building and Using ColdFusion Components...
Page 264: ...264 Chapter 12 Building Custom CFXAPI Tags...
Page 266: ......
Page 314: ...314 Chapter 14 Handling Errors...
Page 344: ...344 Chapter 15 Using Persistent Data and Locking...
Page 349: ...About user security 349...
Page 357: ...Security scenarios 357...
Page 370: ...370 Chapter 16 Securing Applications...
Page 388: ...388 Chapter 17 Developing Globalized Applications...
Page 408: ...408 Chapter 18 Debugging and Troubleshooting Applications...
Page 410: ......
Page 426: ...426 Chapter 19 Introduction to Databases and SQL...
Page 476: ...476 Chapter 22 Using Query of Queries...
Page 534: ...534 Chapter 24 Building a Search Interface...
Page 556: ...556 Chapter 25 Using Verity Search Expressions...
Page 558: ......
Page 582: ...582 Chapter 26 Retrieving and Formatting Data...
Page 668: ......
Page 734: ...734 Chapter 32 Using Web Services...
Page 760: ...760 Chapter 33 Integrating J2EE and Java Elements in CFML Applications...
Page 786: ...786 Chapter 34 Integrating COM and CORBA Objects in CFML Applications...
Page 788: ......