/ File History
Login
SQLite training in Houston TX on 2019-11-05 (details)
Part of the 2019 Tcl Conference

Many hyperlinks are disabled.
Use anonymous login to enable hyperlinks.

History of test/join5.test

2019-05-18
21:22
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. file: [3a96dc62] check-in: [778b1224] user: dan branch: trunk, size: 9101
2019-02-08
04:15
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]. file: [f8b5ffdf] check-in: [440a7cda] user: drh branch: trunk, size: 8693
2018-12-24
20:21
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. file: [1df0a9b9] check-in: [7153552b] user: drh branch: reuse-subqueries, size: 8345
2018-05-04
00:39
Make a separate limb in the EXPLAIN QUERY PLAN output for the various lines associated with the OR-optimization. file: [5a2da0c3] check-in: [75ac7b4e] user: drh branch: trunk, size: 8307
2018-05-02
18:00
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. file: [196e0cbb] check-in: [5f0e803e] user: drh branch: rework-EQP, size: 8281
2018-04-24
18:53
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). file: [000a18e9] check-in: [ce35e39c] user: dan branch: trunk, size: 8284
14:05
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]. file: [cb052e71] check-in: [b8ef967a] user: dan branch: trunk, size: 7189
2018-03-20
19:02
Fix incorrect testcase labels on two cases in join5.test. No changes to code. file: [c6bd62ef] check-in: [4661ac81] user: drh branch: trunk, size: 6494
2016-12-01
19:38
Avoid clearing the EP_FromJoin flag from terms in ON clauses when flattening sub-selects. Possible fix for [2df0107b]. file: [bc98ea4b] check-in: [8bed4cd5] user: dan branch: left-join-fix, size: 6494
2015-08-22
01:32
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]. file: [8a5c0be6] check-in: [351bc22f] user: drh branch: trunk, size: 5852
2014-12-04
16:27
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]. file: [5df23eba] check-in: [6f6fcbe4] user: drh branch: trunk, size: 5246
2007-06-08
00:20
Fix the query optimizer so that it correctly handles constant expressions in the ON clause of a LEFT JOIN. Ticket #2403. (CVS 4049) file: [86675fc2] check-in: [46fdd195] user: drh branch: trunk, size: 3168
2005-09-19
21:05
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) file: [26468256] check-in: [ea10f978] user: drh branch: trunk, size: 1829 Added