contrib/sqlite3/sqlite3.c

13511   int iLimit, iOffset;   /* Memory registers holding LIMIT & OFFSET counters */
13524   Expr *pOffset;         /* OFFSET expression. NULL means not used. */
24160       sqlite3TreeViewItem(pView, "OFFSET", (n--)>0);
54864 **   OFFSET   SIZE    DESCRIPTION
54935 **   OFFSET   SIZE     DESCRIPTION
80317 ** LIMIT and OFFSET process.  r[P1] holds the limit counter.  r[P3]
80319 ** of the LIMIT and OFFSET and stores that value in r[P2].  The r[P2]
80323 ** If r[P3] is zero or negative, that means there is no OFFSET
86307     /* Resolve the expressions in the LIMIT and OFFSET clauses. These
88252   assert( p->pOffset==0 );               /* No LIMIT means no OFFSET */
99505 ** and LIMIT/OFFSET portion of DELETE and UPDATE statements.
99517   Expr *pOffset,               /* The OFFSET clause.  May be null */
99545   **   DELETE FROM table_a WHERE col1=1 ORDER BY col2 LIMIT 1 OFFSET 1
99548   **     SELECT rowid FROM table_a WHERE col1=1 ORDER BY col2 LIMIT 1 OFFSET 1
110613   Expr *pOffset         /* OFFSET value.  NULL means no offset */
111103 ** Add code to implement the OFFSET
111112     VdbeComment((v, "OFFSET"));
112314 ** that appear in the original SQL statement after the LIMIT and OFFSET
112326 ** of the OFFSET.  The iLimit register is initialized to LIMIT.  Register
112327 ** iOffset+1 is initialized to LIMIT+OFFSET.
112373       VdbeComment((v, "OFFSET counter"));
112375       VdbeComment((v, "LIMIT+OFFSET"));
112476 ** negative LIMIT means to output all rows.  If there is also an OFFSET clause
112477 ** with a positive value, then the first OFFSET outputs are discarded rather
112478 ** than being sent to pDest.  The LIMIT count does not begin until after OFFSET
112501   Expr *pLimit, *pOffset;       /* Saved LIMIT and OFFSET */
112502   int regLimit, regOffset;      /* Registers used by LIMIT and OFFSET */
112507   /* Process the LIMIT and OFFSET clauses, if they exist */
112626 **   (1) It has no LIMIT or OFFSET
113114   /* Suppress the first OFFSET entries if there is an OFFSET clause
113763 **  (14)  The subquery does not use OFFSET.
113783 **        LIMIT and OFFSET clauses.  The subquery cannot use any compound
113877   /* Prior to version 3.1.2, when LIMIT and OFFSET had to be simple constants,
113878   ** not arbitrary expressions, we allowed some combining of LIMIT and OFFSET
113879   ** because they could be computed at compile-time.  But when LIMIT and OFFSET
113999   ** followed by any ORDER BY, LIMIT and/or OFFSET clauses. This block
114001   ** OFFSET clauses and joins them to the left-hand-side of the original
114218     ** SELECT ... FROM (SELECT ... LIMIT a OFFSET b) LIMIT x OFFSET y;
128351   Expr *pOffset;   /* The OFFSET expression.  NULL if there is none */
129188    27,  /*     OFFSET => ID */
129300   "NO",            "KEY",           "OF",            "OFFSET",
129489  /* 132 */ "limit_opt ::= LIMIT expr OFFSET expr",
131004       case 132: /* limit_opt ::= LIMIT expr OFFSET expr */
132286       testcase( i==40 ); /* OFFSET */
163376   int nOffset                     /* Add "LIMIT -1 OFFSET $nOffset" to SELECT */
163387       zLimit = sqlite3_mprintf(" LIMIT -1 OFFSET %d", nOffset);