Lines Matching defs:side
4495 ** choice of query plan if the parameter is the left-hand side of a [LIKE]
4608 ** [virtual tables] might change the database indirectly as a side effect.
4611 ** change the database file through side-effects:
5584 ** functions that have side effects or reveal internal application state.
5726 ** that have side-effects or that could potentially leak sensitive
5733 ** no side effects and should not depend on any values other than its
5737 ** side effects.
5750 ** security-adverse side-effects and information-leaks.
7451 ** expr on the right-hand side can be evaluated (and thus the constraint
7476 ** the right-hand side of the corresponding aConstraint[] is evaluated
7850 ** [UPDATE], [DELETE], or by [ON CONFLICT] side-effects
10094 ** on the right-hand side of the IN operator.)^ Thus the virtual table
10095 ** only sees a single value from the right-hand side of the IN operator
10146 ** [sqlite3_vtab_in_next()] to find all values on the right-hand side
10152 ** CAPI3REF: Find all elements on the right-hand side of an IN constraint.
10169 ** ^(Use these routines to access all values on the right-hand side
10187 ** right hand side of the IN constraint, then *P is set to NULL and these
10217 ** inteface returns SQLITE_NOTFOUND if the right-hand side of the J-th
17379 #define SQLITE_FUNC_UNSAFE 0x00200000 /* Function has side effects */
18903 ** the side-effects of functions.
18999 ** pointer of each autoincrement table to record some side information that
22939 ** set of values on the right-hand side of an IN constraint.
36097 ** for JavaScript-side implementations in WASM builds. In such builds
68750 ** normally produced as a side-effect of SQLITE_CORRUPT_BKPT is augmented
75781 ** in a balancing operation. NN is the number of neighbors on either side
75784 ** NN neighbors on either side.
75796 #define NN 1 /* Number of neighbors on either side of pPage */
76246 ** a new page to the right-hand side and put the one new entry in
76247 ** that page. This leaves the right side of the tree somewhat
76462 ** same amount of free space. Usually a single sibling on either side of the
76464 ** side if the page is the first or last child of its parent. If the page
76554 ** either side of pPage. More siblings are taken from one side, however,
76555 ** if there are fewer than NN siblings on the other side. If pParent
76858 ** on the left side (siblings with smaller keys). The left siblings are
100536 const void *pKey1, int nKey1, /* Left side of comparison */
100537 const void *pKey2, int nKey2 /* Right side of comparison */
100563 const void *pKey1, int nKey1, /* Left side of comparison */
100564 const void *pKey2, int nKey2 /* Right side of comparison */
100582 const void *pKey1, int nKey1, /* Left side of comparison */
100583 const void *pKey2, int nKey2 /* Right side of comparison */
100624 const void *pKey1, int nKey1, /* Left side of comparison */
100625 const void *pKey2, int nKey2 /* Right side of comparison */
105628 ** is replaced by a copy of the left-hand side of the result-set expression.
106085 /* One side is a column, the other is not. Use the columns affinity. */
106855 ** If one side or the other of the AND is known to be false, then instead
108455 ** right-hand side. Return TRUE if that list is constant.
108529 ** might need to know whether or not the RHS side of the IN operator
108639 /* sqlite3CompareAffinity() only returns TEXT if one side or the
108640 ** other has no affinity and the other side is TEXT. Hence,
108847 ** x IN (4,5,11) -- IN operator with list on right-hand side
108882 ** * The right-hand side is a correlated subquery
108883 ** * The right-hand side is an expression list containing variables
109102 ** * The right-hand side is a correlated subquery
109103 ** * The right-hand side is an expression list containing variables
109209 ** The left-hand side (LHS) is a scalar or vector expression. The
109210 ** right-hand side (RHS) is an array of zero or more scalar values, or a
110560 ** really constant because they originate from the right-hand side
111379 ** The pA side might be using TK_REGISTER. If that is the case and pB is
114818 ** side-effect of the CREATE TABLE statement is to leave the rootpage
122420 Token *pAlias, /* The right-hand side of the AS subexpression */
125704 ** its side-effects.
134615 ** If the left side is "database.id" then pId1 is the database name
134616 ** and pId2 is the id. If the left side is just "id" then pId1 is the
138648 ** if the table that p references is on the left side of a RIGHT JOIN.
138778 ** JOINs. If only a single table on the left side of this join
138780 ** But if there are two or more tables on the left side
139367 ** on the right-hand side of an INSERT contains more result columns than
139701 ** user-defined functions that have side effects. We do not care
141995 ** When the subquery on the right side of the LEFT JOIN is flattened, we
142490 int isOuterJoin = 0; /* True if pSub is the right side of a LEFT JOIN */
142676 ** OFFSET clauses and joins them to the left-hand-side of the original
152683 ** the right hand side of the equality constraint (t2.b) has BLOB/NONE affinity,
155077 ** the left-hand side operand in their in-fix form.
155289 ** If there are exactly two disjuncts and one side has x>A and the other side
155480 /* Search for a table and column that appears on one side or the
155539 /* If the right-hand side is also a column, then the affinities
155764 int nLeft; /* Number of elements on left side vector */
156090 ** This is only required if at least one side of the comparison operation
158582 ** an IN constraint where the right-hand side of the IN operator
160452 ** on the right-hand-side of constraint iCons.
160844 ** prevent FROM-clause terms from moving from the right side of
160845 ** a LEFT JOIN over to the left side of that join if the LEFT JOIN
160846 ** is itself on the left side of a RIGHT JOIN.
162113 ** scanning through all values on the right-hand side of the IN.
167680 int yystksz; /* Current side of the stack */
168961 /* For rule J, yyRuleInfoLhs[J] contains the symbol on the left-hand side
169372 ** of symbols on the right-hand side of that rule. */
177597 assert( /*side-effects-ok*/ (x = va_arg(ap,int))!=0 );
178974 ** TODO(shess) That said, it would be nice to have a better query-side
182081 ** Position list *pp1 corresponds to the left-hand side of the NEAR
182935 ** column on the left-hand side of the MATCH operator is column
182937 ** side of the MATCH operator.
184838 ** phrase on the other side of the NEAR operator to pPhrase. For example,
187338 ** that appears on the left-hand-side of the MATCH operator (the default
195977 ** are part of a sub-tree that is the right-hand-side of a NOT operator.
196019 ** indirectly descended from the right-hand-side of a NOT operator). If
202844 /* A MATCH operator. The right-hand-side must be a blob that
206233 unsigned char side; /* 1 for p1, 2 for p2 */
206234 unsigned int idx; /* Which segment within the side */
206253 unsigned char side,
206272 pSeg->side = side;
206294 unsigned char side /* The side of pPoly */
206300 geopolyAddOneSegment(p, x[0], x[1], x[2], x[3], side, i);
206303 geopolyAddOneSegment(p, x[0], x[1], pPoly->a[0], pPoly->a[1], side, i);
206450 iMask ^= pSeg->side;
206456 GEODEBUG(("Segment %d.%d %g->%g\n", pSeg->side, pSeg->idx, pSeg->y, y));
206459 if( pPrev->y>pSeg->y && pPrev->side!=pSeg->side ){
206462 pPrev->side, pPrev->idx,
206463 pSeg->side, pSeg->idx));
206470 iMask ^= pSeg->side;
206476 pThisEvent->pSeg->side, pThisEvent->pSeg->idx,
207634 /* If the left hand side of the regexp operator is NULL,
223149 int fts5yystksz; /* Current side of the stack */
223697 /* For rule J, fts5yyRuleInfoLhs[J] contains the symbol on the left-hand side
223731 ** of symbols on the right-hand side of that rule. */
230589 Fts5Buffer *pLeft, /* Left hand side of comparison */
230590 const u8 *pRight, int nRight /* Right hand side of comparison */