Searched refs:orderByConsumed (Results 1 – 4 of 4) sorted by relevance
7139 int orderByConsumed; /* True if output is already ordered */ member
5897 pIdxInfo->orderByConsumed = 1; in seriesBestIndex()11511 pIdx->orderByConsumed = (iCol==0 || iCol==1); in dbdataBestIndex()11513 pIdx->orderByConsumed = (pIdx->aOrderBy[1].iColumn==1); in dbdataBestIndex()
7452 int orderByConsumed; /* True if output is already ordered */ member151950 sqlite3DebugPrintf(" orderByConsumed=%d\n", p->orderByConsumed);154558 pIdxInfo->orderByConsumed = 0;154622 pIdxInfo->orderByConsumed = 0;154644 pNew->u.vtab.isOrdered = (i8)(pIdxInfo->orderByConsumed ?175038 pInfo->orderByConsumed = 1;179586 pInfo->orderByConsumed = 1;208083 pIdxInfo->orderByConsumed = 1;208866 pIdxInfo->orderByConsumed = 1;231074 pInfo->orderByConsumed = 1;[all …]
82777 + pIdxInfo->orderByConsumed = 1;86600 - pIdxInfo->orderByConsumed = 1;91387 +** the "orderByConsumed" flag.91395 +** the xBestIndex method to set the "orderByConsumed" flag, regardless of91430 +** specified above, then it must not set the "orderByConsumed" flag in the91434 +** it wants, as long as the "orderByConsumed" flag is not set. ^When the91435 +** the "orderByConsumed" flag is unset, the query planner will add extra91437 +** ordered correctly. The use of the "orderByConsumed" flag and the91439 +** use of the sqlite3_vtab_distinct() interface and the "orderByConsumed"91441 +** overly aggressive and setting the "orderByConsumed" flag when it is not[all …]