SQLite

All files named ”test/where7.test”
Login

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

History for test/where7.test

2023-08-03
13:07
[15041c7a58] part of check-in [976e39c632] Fix a test case whose value changes under the no_optimization permutation due to the recent change to add the ability for SQLITE_TESTCTRL_OPTIMIZATION to disable one-pass. (check-in: [976e39c632] user: drh branch: trunk, size: 656228)
2022-03-03
15:59
[1c1bf436bf] part of check-in [61a1c6dbd0] Fix for the problem identified in forum post 0cd8e058bf: When evaluating an multi-index OR, do not push down auxiliary WHERE clause terms that involve subqueries into the OR-subqueries. Otherwise, the covering-index optimizer might convert table-references into index-references for the particular OR index that is active for the branch in which the subquery subroutine is coded, and those index-references will not work if the subquery subroutine is invoked from a different OR branch that uses a different index. (check-in: [61a1c6dbd0] user: drh branch: trunk, size: 655793)
2021-03-20
15:11
[ab41d53ce8] 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: 654845)
2018-12-24
20:21
[75722434c4] 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: 654863)
2018-05-04
00:39
[e579da972e] 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: 654825)
2018-05-02
18:00
[9bfbfdf0ee] 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: 654799)
2015-12-08
04:18
[f520bcec2c] part of check-in [177862c1d5] Add a test case of the form "WHERE a<2 OR a<3" using PRAGMA count_changes. This test case was failing before the 3.9.0 release. (check-in: [177862c1d5] user: drh branch: trunk, size: 654806)
2013-06-12
17:08
[5a4b0abc20] part of check-in [addd7f466d] "make test" now passing. (check-in: [addd7f466d] user: drh branch: nextgen-query-plan-exp, size: 654478)
2013-06-10
23:30
[e0741d85b6] part of check-in [aa580e368e] Fix test cases for the new EXPLAIN QUERY PLAN format. Add the wherecosttest tool. Other fixes to logarithm cost. (check-in: [aa580e368e] user: drh branch: nextgen-query-plan-logcost, size: 654476)
2012-03-09
22:02
[5c566388f0] part of check-in [0dc4cb9355] 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. (check-in: [0dc4cb9355] user: drh branch: trunk, size: 654507)
2011-10-07
16:08
[814d737341] part of check-in [4997d8b81c] More test cases for the OR optimization. (check-in: [4997d8b81c] user: drh branch: or-opt, size: 654506)
2010-11-13
16:42
[aa4cfcd6f6] part of check-in [6611b76b02] 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. (check-in: [6611b76b02] user: dan branch: experimental, size: 654564)
2010-11-11
11:43
[2707b476db] part of check-in [7ae068952f] Fix a bug in the EXPLAIN QUERY PLAN code. (check-in: [7ae068952f] user: dan branch: experimental, size: 654549)
10:36
[23ad8b8bee] part of check-in [30904ef841] Modifications to test cases to account for new EXPLAIN QUERY PLAN output. (check-in: [30904ef841] user: dan branch: experimental, size: 654549)
2010-10-21
03:13
[221fd05b26] part of check-in [1e0db99797] Add new WHERETRACE macros for better diagnostics of the query planner. Added a new test case for the performance regression fixed by the previous check-in. (check-in: [1e0db99797] user: drh branch: trunk, size: 654515)
2010-04-15
01:04
[a0a92b8ce4] part of check-in [defaf0d99a] Further refinements to table order selection on join query planning. (check-in: [defaf0d99a] user: drh branch: trunk, size: 653223)
2009-08-20
18:14
[fdd58ab9de] part of check-in [f0c24b5fb8] Continuing refinements of the range-scan optimizations in where.c. The range scores are changed from an integer 1..9 to 0..100. (check-in: [f0c24b5fb8] user: drh branch: trunk, size: 653407)
2009-06-07
23:45
[b6e84b472a] part of check-in [a255c645c4] Disable the LIKE optimization if the affinity of the LHS column is not TEXT. Ticket #3901. (CVS 6727) (check-in: [a255c645c4] user: drh branch: trunk, size: 653389)
2009-04-21
09:02
[42d5e19c88] part of check-in [f61e4cd936] Attempt to optimize virtual table queries with 'OR' expressions in the WHERE clause. (CVS 6527) (check-in: [f61e4cd936] user: danielk1977 branch: trunk, size: 653387)
2009-01-14
00:55
[2487cda68f] part of check-in [d28b58209b] Make sure the OR-clause optimizer takes the cost of sorting into account. Reset the rowid cache on the OP_Rewind and OP_Last opcodes. Bump the version number so that we can do an emergency release. Ticket #3581. (CVS 6173) (check-in: [d28b58209b] user: drh branch: trunk, size: 665398)
2008-12-30
17:55
[88eb7c53bd] part of check-in [b090d5736d] Fix a bug in the multi-index OR cost estimator. Remove leftover "breakpoint" commands from test scripts. (CVS 6086) (check-in: [b090d5736d] user: drh branch: trunk, size: 665235)
14:40
[c56c34e84f] part of check-in [eb9ba5fe70] Still more test cases in where7.test. (CVS 6080) (check-in: [eb9ba5fe70] user: drh branch: trunk, size: 664997)
14:14
[696b4849b2] part of check-in [174985831f] Add many new test cases to where7.test. (CVS 6079) (check-in: [174985831f] user: drh branch: trunk, size: 663671)
2008-12-28
20:47
[3ed6a8cb7d] part of check-in [3464d369d3] Multi-index OR optimizer response to ORDER BY rowid. But fix in sqlite3_stmt_status(): report a full table scan when "ORDER BY rowid" is used without constraints. (CVS 6069) (check-in: [3464d369d3] user: drh branch: trunk, size: 2823)
18:35
[c27e4865d6] part of check-in [67cf24b30e] Optimize WHERE clauses that constain AND, BETWEEN, and LIKE terms as operands of an OR. (CVS 6068) (check-in: [67cf24b30e] user: drh branch: trunk, size: 2430)
2008-12-23
23:56
Added: [b04da5cee0] part of check-in [55d4f493e7] Continuing improvements to the multi-index OR-clause optimizer. Added a few simple test cases. (CVS 6062) (check-in: [55d4f493e7] user: drh branch: trunk, size: 2193)