Many hyperlinks are disabled.
Use anonymous login to enable hyperlinks.
7 check-ins related to "defer-where-subqueries"
|17:00||When multiple constraints need to be evaluated for a row, do any constraints that involve correlated subqueries last. Hence, the priority is index-covered constraints first, correlated subquery constraints last, and all others in the middle. This is a follow-on and improvement to the push-down optimization of check-in [d7bb79ed]. (check-in: c4cb9048 user: drh tags: trunk)|
|16:38||Additional debugging Noop-comment in the constraint generator when wheretrace is enabled. (Closed-Leaf check-in: 0ca7474f user: drh tags: defer-where-subqueries)|
|15:26||Small performance optimization in sqlite3WhereExprUsage(). (check-in: 38edc677 user: drh tags: defer-where-subqueries)|
|15:17||Fix another problem on this branch. (check-in: a4fc9811 user: dan tags: defer-where-subqueries)|
|14:39||Fix a problem causing non-covered WHERE terms to be evaluated before covered WHERE terms. (check-in: 7d3cb39f user: dan tags: defer-where-subqueries)|
|14:33||When testing non-indexed WHERE constraints, test those that involve correlated sub-queries last of all. This increases the chances of not having to run the sub-query at all. (check-in: 1f9c1f35 user: dan tags: defer-where-subqueries)|
|13:24||For sqlite3TreeView() debugging output, show the Expr.flags field on scalar subqueries. (check-in: dc857a96 user: drh tags: trunk)|