Many hyperlinks are disabled.
Use anonymous login
to enable hyperlinks.
7 check-ins related to "nextgen-query-plan-logcost"
2013-06-11
| ||
02:36 | Use a logarithmic rather than linear cost and row-count measures. Do not report row count estimates in EQP output. (check-in: b777b109 user: drh tags: nextgen-query-plan-exp) | |
02:32 | Fixes to EXPLAIN QUERY PLAN output. Change weights back to something closer to what they are in legacy. More test case fixes. (Closed-Leaf check-in: 36373b85 user: drh tags: nextgen-query-plan-logcost) | |
01:50 | Handle virtual tables correctly when using logarithmic costs. Fixes to test cases. (check-in: e612664a user: drh tags: nextgen-query-plan-logcost) | |
2013-06-10
| ||
23:30 | Fix test cases for the new EXPLAIN QUERY PLAN format. Add the wherecosttest tool. Other fixes to logarithm cost. (check-in: aa580e36 user: drh tags: nextgen-query-plan-logcost) | |
20:46 | Fix some minor issues with logarithmic cost in NGQP. (check-in: 69cf8772 user: drh tags: nextgen-query-plan-logcost) | |
19:12 | First attempt to store costs and row counts as a logarithm. (check-in: 9e810967 user: drh tags: nextgen-query-plan-logcost) | |
14:56 | Simplification and performance tweak to the high-speed NGQP bypass. (check-in: 0f8a38ee user: drh tags: nextgen-query-plan-exp) | |