|
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, 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 |
|
| #
607dd6e6 |
| 03-Jan-2020 |
dan <[email protected]> |
Fix a possible NULL pointer dereference caused by using a "VALUES(...)" as a component of a compound SELECT with non-integer ORDER BY clause terms.
FossilOrigin-Name: 9d791116420f4e3f613775569e0a0cb
Fix a possible NULL pointer dereference caused by using a "VALUES(...)" as a component of a compound SELECT with non-integer ORDER BY clause terms.
FossilOrigin-Name: 9d791116420f4e3f613775569e0a0cba2fc22da568b2fb2df920bcf9c9002938
show more ...
|
|
Revision tags: 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, 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 |
|
| #
c6f36fa3 |
| 05-May-2018 |
drh <[email protected]> |
In an ORDER BY LIMIT, make sure the ORDER BY expression evaluator does not
try to reuse values from the result set if the result set has not yet
be computed. This fixes a bug in the recent deferred-
In an ORDER BY LIMIT, make sure the ORDER BY expression evaluator does not
try to reuse values from the result set if the result set has not yet
be computed. This fixes a bug in the recent deferred-row loading
optimization, check-in [c381f0ea57002a264fd958b28e].
OSSFuzz discovered the problem.
FossilOrigin-Name: 5d61e75f32de09c81dbe844443209f063cccb005d60b846900de5b023643fc3b
show more ...
|
| #
fa16f5d9 |
| 03-May-2018 |
drh <[email protected]> |
Enhance EXPLAIN QUERY PLAN to report the generation of constant rows using
VALUES or just a SELECT without FROM.
FossilOrigin-Name: c75eee69fa8a9b56ee58a4cc539e80cc982f43390dc3a357344d58479dd89a41
|
| #
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 |
|
| #
a04a8be2 |
| 13-Jan-2016 |
drh <[email protected]> |
When the [https://www.sqlite.org/queryplanner.html#partialsort|block sorting optimization]
is used in a scalar subquery, be sure to exit the loop as soon as the first
valid output row is received. F
When the [https://www.sqlite.org/queryplanner.html#partialsort|block sorting optimization]
is used in a scalar subquery, be sure to exit the loop as soon as the first
valid output row is received. Fix for ticket [cb3aa0641d9a4].
FossilOrigin-Name: cdbb0947f9ce18d6d7e29ffab5ea6a2ee5365fbb
show more ...
|
|
Revision tags: 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 |
|
| #
11b04817 |
| 12-Apr-2015 |
drh <[email protected]> |
Avoid problems when a query has a GROUP BY and an ORDER BY but no FROM clause.
FossilOrigin-Name: e527d96a1e098ade4e9d124b630a8c2ea2ac9b36
|
| #
96974bd3 |
| 11-Apr-2015 |
dan <[email protected]> |
Fix a problem with sorting large amounts of partially ordered data.
FossilOrigin-Name: acca97efda86a0c020854d2dd9da16f5879986b1
|
|
Revision tags: 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 |
|
| #
137fd4fd |
| 19-Sep-2014 |
drh <[email protected]> |
Make sure that the sorting-index pre-filter recognizes that a rowid reference
might be sortable. This fixes a performance regression.
FossilOrigin-Name: 72727b68cd07969165f1f0943cc7e1a265436653
|
|
Revision tags: version-3.8.6, version-3.8.5 |
|
| #
d0dc5d49 |
| 03-Jun-2014 |
drh <[email protected]> |
Avoid closing a pseudo-table associated with sorting in a co-routine since
that pseudo-table might be used again in an outer loop.
FossilOrigin-Name: 6d81805298ea882f5fee99504d5a95f1a762a90b
|
| #
2504c6c6 |
| 02-Jun-2014 |
drh <[email protected]> |
Fix the query planner so that it once again knows that queries without a
FROM clause will never return more than one row and hence do not require
sorting.
FossilOrigin-Name: 9f18b303cd1bc5779d826698
Fix the query planner so that it once again knows that queries without a
FROM clause will never return more than one row and hence do not require
sorting.
FossilOrigin-Name: 9f18b303cd1bc5779d82669884f802c7889b4947
show more ...
|
|
Revision tags: 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
|
| #
aec93a1f |
| 04-Jun-2013 |
drh <[email protected]> |
Test case updates.
FossilOrigin-Name: 0360fec7c093870269211447e9642b5ee34ff778
|
|
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 |
|
| #
782d68a4 |
| 09-Nov-2012 |
drh <[email protected]> |
Try to take into account the cost of inner loops when selecting which table
of a join to use for the outer loop.
FossilOrigin-Name: 942556342a332b04a11169bb04f387d741ef9488
|
| #
2fad815c |
| 08-Oct-2012 |
drh <[email protected]> |
All test cases (veryquick.tcl and min.rc) pass. A few branch operations in
ORDER BY optimization logic are untested by min.rc.
FossilOrigin-Name: 8314fd6078a3a71aea9d6386ff277cfeb592b4ba
|
|
Revision tags: version-3.7.14.1 |
|
| #
afcd522a |
| 02-Oct-2012 |
drh <[email protected]> |
More lenient handling of ORDER BY optimization in joins with mixed ASC/DESC.
This is a better and less restrictive fix for the problem addressed by
the previous check-in.
FossilOrigin-Name: abcf6a5d
More lenient handling of ORDER BY optimization in joins with mixed ASC/DESC.
This is a better and less restrictive fix for the problem addressed by
the previous check-in.
FossilOrigin-Name: abcf6a5d054559ee5a093ba39180c47b4958d9cd
show more ...
|
| #
178eb61c |
| 02-Oct-2012 |
drh <[email protected]> |
Only continue an ORDER BY optimization into inner loops if the equality
constraints on the inner loop match terms of an outer ordered index that
are actually used by the ORDER BY clause.
FossilOrigi
Only continue an ORDER BY optimization into inner loops if the equality
constraints on the inner loop match terms of an outer ordered index that
are actually used by the ORDER BY clause.
FossilOrigin-Name: b0e7b4df6c2a8c479f8d210bde50c737eaa248f0
show more ...
|
| #
5343b2d4 |
| 27-Sep-2012 |
drh <[email protected]> |
More test cases an bug fixes for the ORDER BY optimization of joins. All
veryquick tests now pass.
FossilOrigin-Name: 0d573320057b0903a5589cabfb1b1ece1c57958e
|
| #
6b10a6a7 |
| 27-Sep-2012 |
drh <[email protected]> |
Test cases and bug fixes applied to the ORDER BY optimization for joins.
Some test cases fail, but except for the new orderby1.test failures, all
failures appear to be issues with the tests, not with
Test cases and bug fixes applied to the ORDER BY optimization for joins.
Some test cases fail, but except for the new orderby1.test failures, all
failures appear to be issues with the tests, not with the core code.
FossilOrigin-Name: 75cda864ededb6dc0f84bd52ed3311753a58e351
show more ...
|