|
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 |
|
| #
8aa7f4d8 |
| 03-May-2022 |
drh <> |
Fix the Bloom filter pull-down optimization so that it jumps to the correct
place if it encounters a NULL key. Fix for the bug described by
[forum:/forumpost/2482b32700384a0f|forum thread 2482b32700
Fix the Bloom filter pull-down optimization so that it jumps to the correct
place if it encounters a NULL key. Fix for the bug described by
[forum:/forumpost/2482b32700384a0f|forum thread 2482b32700384a0f].
FossilOrigin-Name: 6eda9b1a7784cf6d58c8876551f67ab98e78a08e726a0579d4def5ba881985bb
show more ...
|
|
Revision tags: 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 |
|
| #
be341502 |
| 25-Mar-2022 |
drh <> |
Fix the Bloom-filter optimization so that it does not use IS NULL or
IS NOT NULL constraints from the WHERE clause when operating on a LEFT JOIN.
[forum:/forumpost/031e262a89b6a9d2|Forum thread 031e2
Fix the Bloom-filter optimization so that it does not use IS NULL or
IS NOT NULL constraints from the WHERE clause when operating on a LEFT JOIN.
[forum:/forumpost/031e262a89b6a9d2|Forum thread 031e262a89b6a9d2].
FossilOrigin-Name: 1a6328f2a5b4973094e5f85787145d652119822c86ec01a61f3f985c9d2903f2
show more ...
|
|
Revision tags: version-3.38.1 |
|
| #
56945695 |
| 02-Mar-2022 |
drh <> |
Bloom filter pull-down optimization is incompatible with Skip-Scan.
Make sure the query planner does not try to to both.
[forum:/info/50a1bbe08ce4c29c|Forum post 50a1bbe08ce4c29c].
FossilOrigin-Name
Bloom filter pull-down optimization is incompatible with Skip-Scan.
Make sure the query planner does not try to to both.
[forum:/info/50a1bbe08ce4c29c|Forum post 50a1bbe08ce4c29c].
FossilOrigin-Name: ad3ffa1a75a5a032ebb64d8e014ee0a85c5e44b732e4b11bd67f31a59e729b94
show more ...
|
|
Revision tags: version-3.38.0 |
|
| #
87fb37ef |
| 31-Jan-2022 |
drh <> |
Do not attempt to limit the number of columns used in a table to a prefix
if the table will be used to construct an automatic index or bloom filter.
dbsqlfuzz 787d9bd73164c6f0c85469e2e48b2aff19af6938
Do not attempt to limit the number of columns used in a table to a prefix
if the table will be used to construct an automatic index or bloom filter.
dbsqlfuzz 787d9bd73164c6f0c85469e2e48b2aff19af6938.
FossilOrigin-Name: f8766231d2a77bb8b95726b514736d4c2d20b056f7fe60bdbc98ebf5e5b15ae9
show more ...
|
|
Revision tags: version-3.37.2, version-3.37.1 |
|
| #
a11c5e22 |
| 09-Dec-2021 |
drh <> |
Enable bloom filters for the right table of a LEFT JOIN. Fix unreachable
branches.
FossilOrigin-Name: d342ab722de1fc3f34219c9755253db9d88eb50a6fa5cc257207008b00e7fc03
|
|
Revision tags: 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 |
|
| #
7ac0e562 |
| 18-May-2019 |
dan <[email protected]> |
Fix an assert() failure that could occur in a join query if the RHS of an IN() operator is a list containing correlated expressions. This problem was introduced by checkin [e130319317e7611938] which
Fix an assert() failure that could occur in a join query if the RHS of an IN() operator is a list containing correlated expressions. This problem was introduced by checkin [e130319317e7611938] which was part of the fix for ticket [787fa716be3a7f650c] - so this commit is part of that ticket's fix too.
FossilOrigin-Name: 778b1224a318d0137c7dab8361128f593506d3677267898119b934b4d66dfe38
show more ...
|
|
Revision tags: version-3.28.0, version-3.27.2, version-3.27.1 |
|
| #
8851e100 |
| 08-Feb-2019 |
drh <[email protected]> |
Do not do the optimization that attempts to pull expression values from
an index on that expression when processing a multi-index OR
(see check-in [a47efb7c8520a0111]) because the expression transfor
Do not do the optimization that attempts to pull expression values from
an index on that expression when processing a multi-index OR
(see check-in [a47efb7c8520a0111]) because the expression transformations
that are applied become invalid when the processing moves off of the current
index and on to the next index. Fix for ticket [4e8e4857d32d401f].
FossilOrigin-Name: 440a7cda000164d3b46109caf2e1dde80681ba9b0d94ba9be6847d2b917445cf
show more ...
|
|
Revision tags: 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 ...
|
| #
820fcd2c |
| 24-Apr-2018 |
dan <[email protected]> |
Fix a problem with processing "LEFT JOIN tbl ON tbl.a = ? AND (tbl.b=? OR
tbl.c=?)" in cases where there are indexes on both tbl(a, b) and tbl(a, c).
FossilOrigin-Name: ce35e39c5cc2b00dd6b4a9ffaa9d5
Fix a problem with processing "LEFT JOIN tbl ON tbl.a = ? AND (tbl.b=? OR
tbl.c=?)" in cases where there are indexes on both tbl(a, b) and tbl(a, c).
FossilOrigin-Name: ce35e39c5cc2b00dd6b4a9ffaa9d5eb7d9b862759e87d5f053729de7643eee9c
show more ...
|
| #
4da04f78 |
| 24-Apr-2018 |
dan <[email protected]> |
Do not attempt to read values from indexes-on-expressions if the index is on
the RHS of a LEFT JOIN. This won't work if the index cursor points at a
null-row. Fix for [7fa80496].
FossilOrigin-Name:
Do not attempt to read values from indexes-on-expressions if the index is on
the RHS of a LEFT JOIN. This won't work if the index cursor points at a
null-row. Fix for [7fa80496].
FossilOrigin-Name: b8ef967ab1bebf2846c06c4f7200d6fa1c60e52e55711ea171c25ef1331f8a24
show more ...
|
|
Revision tags: version-3.23.1, version-3.23.0 |
|
| #
f6e6f023 |
| 20-Mar-2018 |
drh <[email protected]> |
Fix incorrect testcase labels on two cases in join5.test. No changes to code.
FossilOrigin-Name: 4661ac81c9589b06a07df8b7931fbd0a7f9a4e9ba1448192b70701dc85a29bd2
|
|
Revision tags: 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 |
|
| #
92ddb3bd |
| 01-Dec-2016 |
dan <[email protected]> |
Avoid clearing the EP_FromJoin flag from terms in ON clauses when flattening
sub-selects. Possible fix for [2df0107b].
FossilOrigin-Name: 8bed4cd549759a93c4a087d8d8c08c0068ba8d59
|
|
Revision tags: 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 |
|
| #
38978dd4 |
| 22-Aug-2015 |
drh <[email protected]> |
Do not apply the WHERE-clause pushdown optimization to terms that originate
in the ON or USING clause of a LEFT JOIN. Fix for ticket
[6df18e949d3676290].
FossilOrigin-Name: 351bc22fa9b5a2e50da3583a
Do not apply the WHERE-clause pushdown optimization to terms that originate
in the ON or USING clause of a LEFT JOIN. Fix for ticket
[6df18e949d3676290].
FossilOrigin-Name: 351bc22fa9b5a2e50da3583a882c5aa390bda19f
show more ...
|
|
Revision tags: 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 |
|
| #
72673a24 |
| 04-Dec-2014 |
drh <[email protected]> |
If a table is the right operand of a LEFT JOIN, then any column of that
table can be NULL even if that column as a NOT NULL constraint.
Fix for ticket [6f2222d550f5b0ee7ed].
FossilOrigin-Name: 6f6fc
If a table is the right operand of a LEFT JOIN, then any column of that
table can be NULL even if that column as a NOT NULL constraint.
Fix for ticket [6f2222d550f5b0ee7ed].
FossilOrigin-Name: 6f6fcbe4736b9468a495c684d5eebc8bfe5c566a
show more ...
|
|
Revision tags: 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, 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, version-3.7.10, version-3.7.9, 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, experimental, version-3.7.2, fts3-refactor, cvs-to-fossil-cutover, version-3.6.15, version-3.6.10 |
|
| #
0a168377 |
| 08-Jun-2007 |
drh <[email protected]> |
Fix the query optimizer so that it correctly handles constant expressions
in the ON clause of a LEFT JOIN. Ticket #2403. (CVS 4049)
FossilOrigin-Name: 46fdd195483787eef209a9b8ad108eba147be6fa
|
| #
22d6a53a |
| 19-Sep-2005 |
drh <[email protected]> |
ON-clause terms in a LEFT JOIN that restrict only the left table, should not
really restrict the left table but instead rows that fail to meet the condition
to be joined with NULL rows from the right
ON-clause terms in a LEFT JOIN that restrict only the left table, should not
really restrict the left table but instead rows that fail to meet the condition
to be joined with NULL rows from the right table. (CVS 2725)
FossilOrigin-Name: ea10f9785e3c5248dafcc297f3a2c5465b6e0dba
show more ...
|