Lines Matching full:compound
156 ** The maximum number of terms in a compound SELECT statement.
157 ** The code generator for compound SELECT statements does one
3387 ** <dd>The maximum number of terms in a compound SELECT statement.</dd>)^
10938 ** enough information about the compound query is known at that point.
10956 Select *pPrior; /* Prior select in a compound select statement */
10957 Select *pNext; /* Next select to the left in a compound */
10958 Select *pRightmost; /* Right-most select in a compound select statement */
73144 ** on the compound select chain, p->pPrior.
73817 ** ORDER BY of a compound SELECT. The expression has not been
73892 ** Analyze the ORDER BY clause in a compound SELECT statement. Modify
73894 ** and N where N is the number of columns in the compound SELECT.
73899 ** are matched against result set expressions of compound SELECT
74099 int isCompound; /* True if p is a compound select */
74100 int nCompound; /* Number of compound terms processed so far */
74105 Select *pLeftmost; /* Left-most of SELECT of a compound */
74234 ** the compound have been resolved.
74261 /* Advance to the next term of the compound
74267 /* Resolve the ORDER BY on a compound SELECT after all terms of
74268 ** the compound have been resolved.
75746 if( p->pPrior ) return 0; /* Not a compound SELECT */
90625 return 0; /* SELECT may not be a compound query */
95362 pParse->db, "COMPOUND SUBQUERIES %d AND %d %s(%s)", iSub1, iSub2,
96000 ** the result set for the compound-select statement "p". Return NULL if
96003 ** The collating sequence for the compound select is taken from the
96031 ** This routine is called to process a compound query form from
96036 ** left is p->pPrior. The left query could also be a compound query
96042 ** Example 1: Consider a three-way compound SQL statement.
96058 ** Notice that because of the way SQLite parses compound SELECTs, the
96126 /* Compound SELECTs that have an ORDER BY clause are handled separately.
96189 ** of a 3-way or more compound */
96355 ** temporary tables needed to implement the compound select.
96572 ** Alternative compound select code generator for cases when there
96586 ** of the compound query.
96589 ** of the compound query. (Only generated for UNION and
96850 ** left of the compound operator - the "A" select.
96878 ** select as the next output row of the compound select.
96886 ** select as the next output row of the compound select.
96993 /* Reassembly the compound query so that it will be freed correctly
97162 ** (15) The outer query is not part of a compound select or the
97170 ** (17) The sub-query is not a compound select, or it is a UNION ALL
97171 ** compound clause made up entirely of non-aggregate queries, and
97174 ** * is not itself part of a compound select,
97180 ** LIMIT and OFFSET clauses. The subquery cannot use any compound
97181 ** operator other than UNION ALL because all the other compound
97185 ** (18) If the sub-query is a compound select, then all terms of the
97192 ** (20) If the sub-query is a compound select, then it must not use
97234 assert( p->pPrior==0 ); /* Unable to flatten compound queries */
97309 /* Restriction 17: If the sub-query is a compound SELECT, then it must
97311 ** that make up the compound SELECT are allowed to be aggregate or distinct
97350 /* If the sub-query is a compound SELECT statement, then (by restrictions
97360 ** select statements in the compound sub-query.
97381 ** We call this the "compound-subquery flattening".
97443 /* The following loop runs once for each term in a compound-subquery
97445 ** of flattening - a flattening other than a compound-subquery flattening -
98417 sqlite3ErrorMsg(pParse, "too many terms in compound SELECT");
102764 #define WO_SINGLE 0x0ff /* Mask of all non-compound WO_* values */
