|
Revision tags: release, version-3.50.2, version-3.50.1, major-release, version-3.50.0, version-3.49.2, patch-release, version-3.44.4, version-3.49.1, version-3.49.0, major-relase, relase, version-3.48.0, version-3.47.2, version-3.47.1, version-3.47.0, version-3.46.1, version-3.46.0, version-3.45.3, version-3.44.3, version-3.45.2, version-3.45.1, vesion-3.45.1, version-3.45.0, version-3.44.2, version-3.44.1, version-3.44.0, version-3.43.2, version-3.43.1, version-3.43.0, version-3.42.0, version-3.41.2, version-3.41.1, version-3.41.0, version-3.40.1, version-3.40.0, version-3.39.4, version-3.39.3, version-3.39.2, version-3.39.1, version-3.39.0, version-3.38.5, version-3.38.4, relese, version-3.38.3, version-3.38.2, version-3.38.1 |
|
| #
c9bcc5aa |
| 03-Mar-2022 |
drh <> |
Fix for the problem identified in
[forum:/forumpost/0cd8e058bf|forum post 0cd8e058bf]:
When evaluating an multi-index OR, do not push down auxiliary WHERE clause
terms that involve subqueries into t
Fix for the problem identified in
[forum:/forumpost/0cd8e058bf|forum post 0cd8e058bf]:
When evaluating an multi-index OR, do not push down auxiliary WHERE clause
terms that involve subqueries into the OR-subqueries. Otherwise, the
covering-index optimizer might convert table-references into index-references
for the particular OR index that is active for the branch in which the
subquery subroutine is coded, and those index-references
will not work if the subquery subroutine is invoked from a different OR branch
that uses a different index.
FossilOrigin-Name: 61a1c6dbd089979cbeb8b0c0c5ee1ab1abcb466be1d21a3a851be73c27e67a6c
show more ...
|
|
Revision tags: version-3.38.0, version-3.37.2, version-3.37.1, version-3.37.0, version-3.36.0, version-3.35.5, version-3.35.4, version-3.35.3, same-as-3.35.3 |
|
| #
8210233c |
| 20-Mar-2021 |
drh <> |
Revise tests cases to align with the new EXPLAIN QUERY PLAN output.
FossilOrigin-Name: 50fbd532602d2c316813046ed6be8be2991c281eb5f295c4c28520a0de73862c
|
|
Revision tags: version-3.35.2, version-3.35.1, version-3.35.0, patch, version-3.34.1, version-3.34.0, version-3.33.0, version-3.32.3, version-3.32.2, version-3.32.1, version-3.32.0, version-3.31.1, version-3.31.0, version-3.30.1, version-3.30.0, version-3.29.0, version-3.28.0, version-3.27.2, version-3.27.1, version-3.27.0 |
|
| #
bd462bcc |
| 24-Dec-2018 |
drh <[email protected]> |
Improvements to EXPLAIN QUERY PLAN formatting. The MULTI-INDEX OR now shows
a separate "INDEX" subtree for each index. SCALAR SUBQUERY entries provide
a subquery number that is related back to the
Improvements to EXPLAIN QUERY PLAN formatting. The MULTI-INDEX OR now shows
a separate "INDEX" subtree for each index. SCALAR SUBQUERY entries provide
a subquery number that is related back to the .selecttrace output.
FossilOrigin-Name: 7153552bac51295c56a1c42ca79d57195851e232509f9e9610375692f48c7e86
show more ...
|
|
Revision tags: version-3.26.0, version-3.25.3, version-3.25.2, version-3.25.1, version-3.25.0, version-3.24.0, version-3.23.2 |
|
| #
5d72d924 |
| 04-May-2018 |
drh <[email protected]> |
Make a separate limb in the EXPLAIN QUERY PLAN output for the various lines
associated with the OR-optimization.
FossilOrigin-Name: 75ac7b4e4fd0811ca80c719badacff207e0bbd00ac64dde3b3d4ec676fad472d
|
| #
b3f0276b |
| 02-May-2018 |
drh <[email protected]> |
Fix test cases so that they work with the new EXPLAIN QUERY PLAN output
format. Only some of the cases have been fixed. This is an incremental
check-in.
FossilOrigin-Name: 5f0e803e33aa557865d5fc83
Fix test cases so that they work with the new EXPLAIN QUERY PLAN output
format. Only some of the cases have been fixed. This is an incremental
check-in.
FossilOrigin-Name: 5f0e803e33aa557865d5fc830d9202d628de9a94c9757058ca48f1a560702cd3
show more ...
|
|
Revision tags: version-3.23.1, version-3.23.0, version-3.22.0, version-3.21.0, version-3.20.1, version-3.19.4, version-3.20.0, version-3.18.2, version-3.18.1, version-3.19.3, version-3.19.2, version-3.19.1, version-3.19.0, version-3.18.0, version-3.17.0, version-3.16.2, version-3.16.1, version-3.16.0, version-3.15.2, version-3.15.1, version-3.15.0, version-3.14.2, version-3.14.1, version-3.14.0, version-3.13.0, version-3.12.2, version-3.12.1, version-3.9.3, version-3.12.0, version-3.11.1, version-3.11.0, version-3.10.2, version-3.10.1, version-3.10.0 |
|
| #
92a82771 |
| 08-Dec-2015 |
drh <[email protected]> |
Add a test case of the form "WHERE a<2 OR a<3" using PRAGMA count_changes.
This test case was failing before the 3.9.0 release.
FossilOrigin-Name: 177862c1d50ba899d890fbc35f35e7423bc6aed5
|
|
Revision tags: version-3.9.2, version-3.9.1, version-3.9.0, version-3.8.11.1, version-3.8.11, version-3.8.10.2, version-3.8.10.1, version-3.8.10, version-3.8.9, version-3.8.8.3, version-3.8.8.2, version-3.8.8.1, version-3.8.8, version-3.8.7.4, version-3.8.7.3, version-3.8.7.2, version-3.8.7.1, version-3.8.6.1, version-3.8.7, version-3.8.6, version-3.8.5, version-3.8.4.3, version-3.8.4.2, version-3.8.4.1, version-3.8.4, version-3.8.3.1, version-3.8.3, version-3.8.2, version-3.8.1, version-3.8.0.2, version-3.8.0.1, version-3.8.0 |
|
| #
4fe425ad |
| 12-Jun-2013 |
drh <[email protected]> |
"make test" now passing.
FossilOrigin-Name: addd7f466d6ff55f82d907286650c26b06e9397b
|
| #
5822d6fe |
| 10-Jun-2013 |
drh <[email protected]> |
Fix test cases for the new EXPLAIN QUERY PLAN format. Add the
wherecosttest tool. Other fixes to logarithm cost.
FossilOrigin-Name: aa580e368e3c398b8377b80342dfdd906324c248
|
|
Revision tags: version-3.7.17, version-3.7.16.2, version-3.7.16.1, version-3.7.16, version-3.7.15.2, version-3.7.15.1, version-3.7.15, version-3.7.14.1, version-3.7.14, version-3.7.13, version-3.7.12.1, version-3.7.12, mountain-lion, version-3.7.11 |
|
| #
331b67c1 |
| 09-Mar-2012 |
drh <[email protected]> |
Candidate fix for the optimizer problem described in ticket
[b7c8682cc17f3] which can causes a LEFT JOIN to be changed
into a INNER JOIN if there are OR terms in the WHERE clause.
FossilOrigin-Name
Candidate fix for the optimizer problem described in ticket
[b7c8682cc17f3] which can causes a LEFT JOIN to be changed
into a INNER JOIN if there are OR terms in the WHERE clause.
FossilOrigin-Name: 0dc4cb935514131c99172175d57feec3a1743aa9
show more ...
|
|
Revision tags: version-3.7.10, version-3.7.9 |
|
| #
85ae206e |
| 07-Oct-2011 |
drh <[email protected]> |
More test cases for the OR optimization.
FossilOrigin-Name: 4997d8b81cd3ea7c708911bfece00020d11224f9
|
|
Revision tags: version-3.7.8, version-3.7.7.1, version-3.7.7, version-3.7.6.3, version-3.7.6.2, version-3.7.6.1, version-3.7.6, version-3.7.5, version-3.7.4 |
|
| #
4bc39fa1 |
| 13-Nov-2010 |
dan <[email protected]> |
Change the EXPLAIN QUERY PLAN output to use "USING INDEX" instead of "BY INDEX", and to use "SEARCH" instead of "SCAN" for loops that are not full-table scans.
FossilOrigin-Name: 6611b76b0296875fb99
Change the EXPLAIN QUERY PLAN output to use "USING INDEX" instead of "BY INDEX", and to use "SEARCH" instead of "SCAN" for loops that are not full-table scans.
FossilOrigin-Name: 6611b76b0296875fb9903b25dfaa783a9c12eaa1
show more ...
|
| #
acf1987d |
| 11-Nov-2010 |
dan <[email protected]> |
Fix a bug in the EXPLAIN QUERY PLAN code.
FossilOrigin-Name: 7ae068952fba4395b4aa437613a5ed2bd9ddf941
|
| #
47eb16d4 |
| 11-Nov-2010 |
dan <[email protected]> |
Modifications to test cases to account for new EXPLAIN QUERY PLAN output.
FossilOrigin-Name: 30904ef8412348464e893e9e1551ef22cad24a3e
|
| #
020efb16 |
| 21-Oct-2010 |
drh <[email protected]> |
Add new WHERETRACE macros for better diagnostics of the query planner.
Added a new test case for the performance regression fixed by the previous
check-in.
FossilOrigin-Name: 1e0db99797be2821716de71
Add new WHERETRACE macros for better diagnostics of the query planner.
Added a new test case for the performance regression fixed by the previous
check-in.
FossilOrigin-Name: 1e0db99797be2821716de7138931ebd5cf8fa63b
show more ...
|
|
Revision tags: experimental, version-3.7.2 |
|
| #
ed754ce2 |
| 15-Apr-2010 |
drh <[email protected]> |
Further refinements to table order selection on join query planning.
FossilOrigin-Name: defaf0d99a807027f8883bf821b6482025f9f54e
|
|
Revision tags: fts3-refactor |
|
| #
98cdf626 |
| 20-Aug-2009 |
drh <[email protected]> |
Continuing refinements of the range-scan optimizations in where.c.
The range scores are changed from an integer 1..9 to 0..100.
FossilOrigin-Name: f0c24b5fb86940f1a88adfb39cc4b9cbfcc66f8a
|
|
Revision tags: cvs-to-fossil-cutover, version-3.6.15 |
|
| #
c4ac22e9 |
| 07-Jun-2009 |
drh <[email protected]> |
Disable the LIKE optimization if the affinity of the LHS column is
not TEXT. Ticket #3901. (CVS 6727)
FossilOrigin-Name: a255c645c46ae03b65f862858fe57e462076e1fc
|
| #
1d46146b |
| 21-Apr-2009 |
danielk1977 <[email protected]> |
Attempt to optimize virtual table queries with 'OR' expressions in the WHERE clause. (CVS 6527)
FossilOrigin-Name: f61e4cd93682fd98bea2a71d346f9eaa68454390
|
|
Revision tags: version-3.6.10 |
|
| #
a7e77061 |
| 14-Jan-2009 |
drh <[email protected]> |
Make sure the OR-clause optimizer takes the cost of sorting into account.
Reset the rowid cache on the OP_Rewind and OP_Last opcodes. Bump the
version number so that we can do an emergency release.
Make sure the OR-clause optimizer takes the cost of sorting into account.
Reset the rowid cache on the OP_Rewind and OP_Last opcodes. Bump the
version number so that we can do an emergency release. Ticket #3581. (CVS 6173)
FossilOrigin-Name: d28b58209bf5eb575d0cad8dc71ac043395c6471
show more ...
|
| #
04bbcd5c |
| 30-Dec-2008 |
drh <[email protected]> |
Fix a bug in the multi-index OR cost estimator. Remove leftover "breakpoint"
commands from test scripts. (CVS 6086)
FossilOrigin-Name: b090d5736d7eaec17a39d3133e1587b1d2a42acb
|
| #
239080fb |
| 30-Dec-2008 |
drh <[email protected]> |
Still more test cases in where7.test. (CVS 6080)
FossilOrigin-Name: eb9ba5fe70df56ee00828f7dbaf71ae6f825737d
|
| #
1cfdce1c |
| 30-Dec-2008 |
drh <[email protected]> |
Add many new test cases to where7.test. (CVS 6079)
FossilOrigin-Name: 174985831f9c8f5c393556d3248b01852573abc7
|
| #
ca8c4667 |
| 28-Dec-2008 |
drh <[email protected]> |
Multi-index OR optimizer response to ORDER BY rowid.
But fix in sqlite3_stmt_status(): report a full table scan
when "ORDER BY rowid" is used without constraints. (CVS 6069)
FossilOrigin-Name: 3464d
Multi-index OR optimizer response to ORDER BY rowid.
But fix in sqlite3_stmt_status(): report a full table scan
when "ORDER BY rowid" is used without constraints. (CVS 6069)
FossilOrigin-Name: 3464d369d3b6899ec726cf5b42b68b1dac2ba982
show more ...
|
| #
29435257 |
| 28-Dec-2008 |
drh <[email protected]> |
Optimize WHERE clauses that constain AND, BETWEEN, and LIKE terms as operands
of an OR. (CVS 6068)
FossilOrigin-Name: 67cf24b30e087796cfb0fccf47328e72ade5ecdc
|
| #
23d04d5a |
| 23-Dec-2008 |
drh <[email protected]> |
Continuing improvements to the multi-index OR-clause optimizer. Added a
few simple test cases. (CVS 6062)
FossilOrigin-Name: 55d4f493e7df8515574a75caec9967d6c71b6012
|