Many hyperlinks are disabled.
Use anonymous login
to enable hyperlinks.
6 check-ins related to "having-where-optimization"
|
2017-05-02
| ||
| 16:55 | Move terms of the HAVING clause that reference only columns in the GROUP BY clause over to the WHERE clause, resulting in a faster query plan. (check-in: 47cbb471d0 user: drh tags: trunk) | |
| 16:46 | Additional comments on the sqlite3ExprIsConstantOrGroupBy() routine. No code changes. (Closed-Leaf check-in: 8424492eac user: drh tags: having-where-optimization) | |
|
2017-05-01
| ||
| 19:53 | Remove an unnecessary branch. (check-in: a33179596f user: drh tags: having-where-optimization) | |
| 14:09 | Add extra tests for the optimization on this branch. (check-in: 4921cd9520 user: dan tags: having-where-optimization) | |
|
2017-04-29
| ||
| 20:53 | Automatically transfer terms from the HAVING clause to the WHERE clause of an aggregate query in cases where the result of evaluating the term depends only one one or more of the GROUP BY expressions (and on no other inputs). (check-in: 5375a3ce56 user: dan tags: having-where-optimization) | |
| 15:27 | Evaluate WHERE clause terms that reference only the index before evaluating terms that require the table, and thereby avoid seeking the table row if index terms are false. This is called the "push-down" optimization in the MySQL world, we are told. Do not confuse with [/info/6df18e949d367629|WHERE-clause push-down]. (check-in: d7bb79ed3a user: drh tags: trunk) | |