Many hyperlinks are disabled.
Use anonymous login
to enable hyperlinks.
History for test/join5.test
|
2025-04-10
| ||
| 10:18 | [76f99f69a4] part of check-in [20acd630b9] Remove unnecessary "www." prefixes on domain names in URLs. (check-in: [20acd630b9] user: drh branch: trunk, size: 13023) | |
|
2024-03-19
| ||
| 16:51 | [380d12a935] part of check-in [0c543c51a8] Update test scripts to account for [8fcea4cd]. (check-in: [0c543c51a8] user: dan branch: rowid-in-view, size: 13031) | |
| 15:27 | [f939b2c7f4] part of check-in [495b8c7b08] Update tests to work with SQLITE_ALLOW_ROWID_IN_VIEW. (check-in: [495b8c7b08] user: dan branch: rowid-in-view, size: 13127) | |
|
2023-05-31
| ||
| 18:35 | [7cc3f3595b] part of check-in [f544a8e47c] Improved detection of when the LEFT JOIN strength reduction optimization can be applied. (check-in: [f544a8e47c] user: drh branch: trunk, size: 12994) | |
|
2023-02-05
| ||
| 20:29 | [91f1f4c7d8] part of check-in [e6ab96bd0b] Do not use a Bloom filter if any outer loop lacks STAT1 data, since without STAT1 data, the query planner cannot make an accurate determination of whether or not a Bloom filter will be useful. This fixes the problem reported by forum post 56de336385. (check-in: [e6ab96bd0b] user: drh branch: trunk, size: 12417) | |
|
2022-05-03
| ||
| 14:25 | [e1ada8581c] part of check-in [3dc9fc2f2d] 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 thread 2482b32700384a0f. (check-in: [3dc9fc2f2d] user: drh branch: branch-3.38, size: 12239) | |
| 14:01 | [d22b6cba8f] part of check-in [6eda9b1a77] 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 thread 2482b32700384a0f. (check-in: [6eda9b1a77] user: drh branch: trunk, size: 12269) | |
|
2022-04-11
| ||
| 14:26 | [c4df54e2e2] part of check-in [d91faeffea] Show LEFT and RIGHT JOIN processing in the EXPLAIN QUERY PLAN output. (check-in: [d91faeffea] user: drh branch: right-join, size: 11260) | |
|
2022-03-25
| ||
| 01:23 | [0d63c7e43b] part of check-in [1a6328f2a5] 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 thread 031e262a89b6a9d2. (check-in: [1a6328f2a5] user: drh branch: trunk, size: 11230) | |
|
2022-03-02
| ||
| 21:04 | [3d51c4ae5f] part of check-in [ad3ffa1a75] Bloom filter pull-down optimization is incompatible with Skip-Scan. Make sure the query planner does not try to to both. Forum post 50a1bbe08ce4c29c. (check-in: [ad3ffa1a75] user: drh branch: trunk, size: 10198) | |
|
2022-01-31
| ||
| 15:59 | [37864d5679] part of check-in [f8766231d2] 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. (check-in: [f8766231d2] user: drh branch: trunk, size: 9561) | |
|
2021-12-09
| ||
| 18:44 | [d22395f7d4] part of check-in [d342ab722d] Enable bloom filters for the right table of a LEFT JOIN. Fix unreachable branches. (check-in: [d342ab722d] user: drh branch: bloom-filter, size: 9101) | |
|
2021-03-20
| ||
| 15:11 | [f418fccdfe] part of check-in [50fbd53260] Revise tests cases to align with the new EXPLAIN QUERY PLAN output. (check-in: [50fbd53260] user: drh branch: eqp-improvements, size: 9071) | |
|
2019-05-18
| ||
| 21:22 | [3a96dc62f0] part of check-in [778b1224a3] 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. (check-in: [778b1224a3] user: dan branch: trunk, size: 9101) | |
|
2019-02-08
| ||
| 04:15 | [f8b5ffdf3c] part of check-in [440a7cda00] 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]. (check-in: [440a7cda00] user: drh branch: trunk, size: 8693) | |
|
2018-12-24
| ||
| 20:21 | [1df0a9b94f] part of check-in [7153552bac] 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. (check-in: [7153552bac] user: drh branch: reuse-subqueries, size: 8345) | |
|
2018-05-04
| ||
| 00:39 | [5a2da0c3ea] part of check-in [75ac7b4e4f] Make a separate limb in the EXPLAIN QUERY PLAN output for the various lines associated with the OR-optimization. (check-in: [75ac7b4e4f] user: drh branch: trunk, size: 8307) | |
|
2018-05-02
| ||
| 18:00 | [196e0cbb55] part of check-in [5f0e803e33] 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. (check-in: [5f0e803e33] user: drh branch: rework-EQP, size: 8281) | |
|
2018-04-24
| ||
| 18:53 | [000a18e9cc] part of check-in [ce35e39c5c] 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). (check-in: [ce35e39c5c] user: dan branch: trunk, size: 8284) | |
| 14:05 | [cb052e7126] part of check-in [b8ef967ab1] 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]. (check-in: [b8ef967ab1] user: dan branch: trunk, size: 7189) | |
|
2018-03-20
| ||
| 19:02 | [c6bd62effc] part of check-in [4661ac81c9] Fix incorrect testcase labels on two cases in join5.test. No changes to code. (check-in: [4661ac81c9] user: drh branch: trunk, size: 6494) | |
|
2016-12-01
| ||
| 19:38 | [bc98ea4b4e] part of check-in [8bed4cd549] Avoid clearing the EP_FromJoin flag from terms in ON clauses when flattening sub-selects. Possible fix for [2df0107b]. (check-in: [8bed4cd549] user: dan branch: left-join-fix, size: 6494) | |
|
2015-08-22
| ||
| 01:32 | [8a5c0be6f0] part of check-in [351bc22fa9] 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 [c2a19d81652f40568c]. (check-in: [351bc22fa9] user: drh branch: trunk, size: 5852) | |
|
2014-12-04
| ||
| 16:27 | [5df23eba18] part of check-in [6f6fcbe473] If a table is the right operand of a LEFT JOIN, then any column of that table can be NULL even if that column has a NOT NULL constraint. Fix for ticket [6f2222d550f5b0ee7ed]. (check-in: [6f6fcbe473] user: drh branch: trunk, size: 5246) | |
|
2007-06-08
| ||
| 00:20 | [86675fc291] part of check-in [46fdd19548] Fix the query optimizer so that it correctly handles constant expressions in the ON clause of a LEFT JOIN. Ticket #2403. (CVS 4049) (check-in: [46fdd19548] user: drh branch: trunk, size: 3168) | |
|
2005-09-19
| ||
| 21:05 | Added: [2646825693] part of check-in [ea10f9785e] 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) (check-in: [ea10f9785e] user: drh branch: trunk, size: 1829) | |