The image verification code you entered is incorrect.

Binary Operators



Binary Operators
OperatorSemantic
ORUnion, the set of all elements in either of two sets
ANDIntersection, the set of all elements in both sets
AND:fieldElements in the same node instance of field
JOINSimilar to AND but applicable across different indexes. Returns those elements in both sets which have common primary keys.
JOINrJoin to the right: return a set consisting of those elements in the set to the right that has common primar keys to both
JOINlJoin to the left: as above but from the set to the left.
ANDNOTElements in the one set but NOT in the other
NOTANDA NOTAND B is equivalent to B ANDNOT A
NANDA B NAND := A B AND NOT
XORExclusive Union, elements in either but not both
XNORA B XNOR := A B XOR NOT
ADJMatching terms are adjacent to one another (as stored on the file system)
NEARMatching terms are "near" one another. In fielded indexes this is interpreted as "in same container" (e.g. PEER) but when there are no fields (plain fulltext) it is a (preset) minimal byte offset (as stored on the file system) of one another.
NEAR:numThe matching terms in the sets are within "num" elements as stored on the file system (file offsets). If the value num is an integer its interpreted as bytes (octets). It its a fraction of 1 its % of the length of record
PEERElements in the same (unnamed) final tree leaf node (container). Its like doing an AND:<Anonymous field what I don't know the name or path of>.
PEERaPEER After
PEERbPEER Before
XPEERHits are elements in the intersection (both sets) but not in the same container.
BEFORE, AFTERIn fielded records its like an ordered PEER (PERRb, resp., PEERa).
BEFORE:field, AFTER:fieldWith a named field its like an ordered AND:field.
PROX[:NN]A special case of proximity. PROX -> NEAR but PROX:0 -> PROX:0 -> ADJ. NN may also be specified as %, example 50%.
BEFORE:num, AFTER:numlike NEAR:num but ordered
FOLLOWS, PRECEDESWithin some ordered elements of one another
ONEAR is as above but uses the query order
FARElements a "good distance" away from each other. In fielded indexes its the same as XPEER. In non-fielded indexes (plain fulltext) its a (preset) minimal byte offset (as stored on the file system) from each another.

Reply

  • Allowed HTML tags: <a> <em> <strong> <cite> <code> <ul> <ol> <li> <dl> <dt> <dd>
  • Lines and paragraphs break automatically.
More information about formatting options Captcha Image: you will need to recognize the text in it.
Please type in the letters/numbers that are shown in the image above.