|
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 |
|
| #
c583719b |
| 11-Apr-2022 |
drh <> |
Show LEFT and RIGHT JOIN processing in the EXPLAIN QUERY PLAN output.
FossilOrigin-Name: d91faeffea5cf0585fb71e5311fdcc6b8be85c7e9c732050b4448e617c970101
|
|
Revision tags: version-3.38.2, version-3.38.1, version-3.38.0, version-3.37.2, version-3.37.1, version-3.37.0, version-3.36.0 |
|
| #
93ffb50f |
| 18-May-2021 |
drh <> |
In the MULTI-INDEX OR query plan, code for sub-expressions can sometimes be
generated twice. But for some subqueries, generating code off of the same
tree twice causes problems. So now MULTI-INDEX
In the MULTI-INDEX OR query plan, code for sub-expressions can sometimes be
generated twice. But for some subqueries, generating code off of the same
tree twice causes problems. So now MULTI-INDEX OR makes a copy of the
sub-expressions it uses to avoid code-generating them more than once.
dbsqlfuzz 9ebd2140e7206ff724e665f172faea28af801635.
FossilOrigin-Name: 4a55f72542c8bcc80253aa77043314cecb29d73cb4f51aa80f7811e86cc8ef68
show more ...
|
|
Revision tags: 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 |
|
| #
094afffa |
| 03-Jun-2020 |
drh <[email protected]> |
Improve the query planner so that it is better able to find full
index scan plan when there is an INDEXED BY clause.
FossilOrigin-Name: d901837fea1ed54de43ad59eb47c02cbfd2eb215fc57317b5ea8c22a7df947
Improve the query planner so that it is better able to find full
index scan plan when there is an INDEXED BY clause.
FossilOrigin-Name: d901837fea1ed54de43ad59eb47c02cbfd2eb215fc57317b5ea8c22a7df947c4
show more ...
|
|
Revision tags: version-3.32.1, version-3.32.0, version-3.31.1, version-3.31.0, version-3.30.1, version-3.30.0 |
|
| #
175b8f06 |
| 08-Aug-2019 |
drh <[email protected]> |
Remove support for STAT3. The sqlite_stat3 tables are ignored, if they
exist. STAT4 continues to work as it always has, and as it is a superset of
STAT3 is the recommended replacement.
FossilOrigi
Remove support for STAT3. The sqlite_stat3 tables are ignored, if they
exist. STAT4 continues to work as it always has, and as it is a superset of
STAT3 is the recommended replacement.
FossilOrigin-Name: 1e17ea2fd1df4ad49138c787c8fe3207dd0c25c93f9001d52a9b69f8c12e841c
show more ...
|
|
Revision tags: 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, 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 |
|
| #
299b2468 |
| 12-Aug-2014 |
dan <[email protected]> |
Fix where9.test so that it works with the "no_optimization" permutation.
FossilOrigin-Name: d46adf9d8f741838b9c30f915231d6a3986c3591
|
|
Revision tags: 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 |
|
| #
b50596d6 |
| 08-Oct-2013 |
drh <[email protected]> |
Rollback some of the previous changes in the branch such that the estimated
row sizes are now only used as a tie-breaker for index scans.
FossilOrigin-Name: 65553ff34b41e54d129ff2fee96be714105503c4
|
| #
186ad8cc |
| 08-Oct-2013 |
drh <[email protected]> |
Further refinement of the idea of multiplying run-time cost estimates by
the estimated row size.
FossilOrigin-Name: 18bd6ba96d19de6047baebfa15b1f739577c9ec4
|
|
Revision tags: version-3.8.0.2, version-3.8.0.1 |
|
| #
d41d39f2 |
| 28-Aug-2013 |
drh <[email protected]> |
In the query optimizer, when converting BETWEEN and LIKE/GLOB expressions
into simpler forms for processing, be sure to transfer the LEFT JOIN markings.
Fix for ticket [bc878246eafe0f52c].
FossilOri
In the query optimizer, when converting BETWEEN and LIKE/GLOB expressions
into simpler forms for processing, be sure to transfer the LEFT JOIN markings.
Fix for ticket [bc878246eafe0f52c].
FossilOrigin-Name: caab361ebee5f5c3fdafd9b1abe3d1ab7c5b4db9
show more ...
|
|
Revision tags: version-3.8.0 |
|
| #
8ad169ab |
| 12-Aug-2013 |
dan <[email protected]> |
If ENABLE_STAT3 is defined but ENABLE_STAT4 is not, have ANALYZE create and populate the sqlite_stat3 table instead of sqlite_stat4.
FossilOrigin-Name: cca8bf4372ab7a0258aa5c9397818415c6cf0abf
|
| #
f52bb8d3 |
| 03-Aug-2013 |
dan <[email protected]> |
Begin adding experimental sqlite_stat4 table. This commit is buggy.
FossilOrigin-Name: 2beea303a1d609cd2ff252412c50b966b9e5e8f1
|
| #
74f91d44 |
| 19-Jun-2013 |
drh <[email protected]> |
Add in the cost of doing a table lookup on OR searches. Make test case
changes to deal with difference in STAT3 behavior.
FossilOrigin-Name: d97898e8e3990ae8c1882c9102b57692d8810730
|
| #
fd5874d2 |
| 12-Jun-2013 |
drh <[email protected]> |
Add the "queryplanner" test permutation. Continuing refinements to NGQP.
FossilOrigin-Name: 25e2cde105a19293bdb9c001b48624e5d7f8c4e5
|
| #
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 |
|
| #
b3129fa5 |
| 09-May-2013 |
drh <[email protected]> |
Do not move WHERE clause terms inside OR expressions that are contained
within an ON clause of a LEFT JOIN. Fix for ticket [f2369304e47167e3e].
FossilOrigin-Name: 1128575d0ab24f7023a0f6e6ce4828b9a0
Do not move WHERE clause terms inside OR expressions that are contained
within an ON clause of a LEFT JOIN. Fix for ticket [f2369304e47167e3e].
FossilOrigin-Name: 1128575d0ab24f7023a0f6e6ce4828b9a09a7c6c
show more ...
|
|
Revision tags: version-3.7.16.2, version-3.7.16.1, version-3.7.16, version-3.7.15.2, version-3.7.15.1 |
|
| #
832ee3d4 |
| 18-Dec-2012 |
drh <[email protected]> |
Optimize the degenerate case of a FROM clause table name enclosed all by
itself inside parentheses. Generate code as if the parentheses did not
exist, rather than the old behavior of manifesting the
Optimize the degenerate case of a FROM clause table name enclosed all by
itself inside parentheses. Generate code as if the parentheses did not
exist, rather than the old behavior of manifesting the parenthesized table
into a transient table. Also, tag every FROM-clause SELECT subquery that is
generated by a parenthesized FROM-clause expression using the SF_NestedFrom
flag. The new SF_NestedFrom flag is not yet used for anything.
FossilOrigin-Name: 7fecced466d86a66b0b751c5b5608141e134fe2d
show more ...
|
|
Revision tags: version-3.7.15, version-3.7.14.1 |
|
| #
3f4d1d1b |
| 15-Sep-2012 |
drh <[email protected]> |
Attempt to use a covering index even on a full table scan, under the theory
that the index will be smaller and require less disk I/O and thus be faster.
FossilOrigin-Name: cfaa7bc12847a7006ccc93815f
Attempt to use a covering index even on a full table scan, under the theory
that the index will be smaller and require less disk I/O and thus be faster.
FossilOrigin-Name: cfaa7bc12847a7006ccc93815f2395ad5259744a
show more ...
|
|
Revision tags: 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 ...
|
| #
2f56da3f |
| 13-Feb-2012 |
dan <[email protected]> |
Changes to various test scripts so that veryquick.test runs with OMIT_COMPOUND_SELECT defined.
FossilOrigin-Name: 76bb649ee2633226324130f5898622c348f93769
|
|
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 |
|
| #
083310df |
| 28-Jan-2011 |
drh <[email protected]> |
Change the weighting of binary searches on tables to 1/10th the cost of a
search on an index. Change the assumed reduction in search space from a
indexed range constraint from 1/3rd to 1/4th. Do no
Change the weighting of binary searches on tables to 1/10th the cost of a
search on an index. Change the assumed reduction in search space from a
indexed range constraint from 1/3rd to 1/4th. Do not let the estimated
number of rows drop below 1.
FossilOrigin-Name: 4847c6cb71423248b186ab7842b97c83e2f5fefd
show more ...
|
|
Revision tags: 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 ...
|