Lines Matching full:near
3950 ** the near future and that SQLite should make its own private copy of
15876 /* A memory allocation of a number of bytes which is near the maximum
15879 ** 255 bytes of overhead. SQLite itself will never use anything near
24860 ** of just a small span of bytes near the 1GiB boundary. Whole File Locking
39834 ** probability of damage to near zero but with a write performance reduction.
42011 /* Move the cursor so that it points to an entry near the key
93493 sqlite3ErrorMsg(pParse, "near \"%T\": syntax error", &yymsp[0].minor.yy0);
94075 sqlite3ErrorMsg(pParse, "near \"%T\": syntax error", &TOKEN);
98874 ** containing the results of the NEAR or phrase query in FTS3 doclist
98903 ** "a OR b AND c NOT d NEAR e"
98907 ** "a OR (b AND (c NOT (d NEAR e)))"
99940 ** Merge two position-lists as required by the NEAR operator.
101222 ** nearexpr ::= phrase (NEAR distance_opt nearexpr)*.
101243 ** Default span for NEAR operators.
101485 { "NEAR", 4, 0, FTSQUERY_NEAR }
101520 /* If this is a "NEAR" keyword, check for an explicit nearness. */
101634 ** NEAR
101740 ** binary operator (AND, OR, NOT or NEAR) is encounted when
101765 /* This test catches attempts to make either operand of a NEAR
101769 ** (bracketed expression) NEAR phrase
101770 ** phrase NEAR (bracketed expression)
101962 zBuf += sprintf(zBuf, "NEAR/%d ", pExpr->nNear);
106470 ** Remove entries from the pSnippet structure to account for the NEAR
106472 ** offsets produced by treating all NEAR operators as AND operators.
106474 ** accounting for the NEAR restriction. For example, if the queried
106481 ** A NEAR/0 E
106485 ** is not near enough to an E).
106509 /* The right-hand-side of a NEAR operator is always a phrase. The
106511 ** itself headed by a NEAR operator. The following initializations
106516 ** <col> MATCH '"abc def" NEAR/2 "ghi jkl"'
106669 ** discarded as part of processing the NEAR operator (see the