Many hyperlinks are disabled.
Use anonymous login
to enable hyperlinks.
History for test/pushdown.test
|
2024-12-02
| ||
| 17:21 | [46a626ef1c] part of check-in [bdd408a255] Ensure that the query flattener does not change an ON clause term to a WHERE clause term. Forum post 3f676b1196. Follow-up to [f1eae192315335d7]. (check-in: [bdd408a255] user: dan branch: trunk, size: 10422) | |
|
2024-07-04
| ||
| 16:57 | [84b5257674] part of check-in [2accf32b6e] Be more aggressive about reusing subqueries that appear on the RHS of IN operators that have been replicated due to the predicate push-down optimization. (check-in: [2accf32b6e] user: drh branch: reuse-subqueries, size: 9583) | |
|
2024-07-03
| ||
| 20:30 | [eab987a373] part of check-in [0bb306eb70] When constructing an ephermeral table to use as the right-hand side of an IN operator, also construct a Bloom filter to speed membership testing. (check-in: [0bb306eb70] user: dan branch: bedrock-3.45-in-bloom, size: 6304) | |
| 20:10 | [9e655df51b] part of check-in [c10a1b99d4] Show the creation of IN-operator Bloom filters in the EXPLAIN QUERY PLAN output. (check-in: [c10a1b99d4] user: drh branch: in-bloom, size: 9989) | |
|
2024-04-07
| ||
| 10:30 | [3330746a89] part of check-in [27865e316f] Merge trunk enhancements into the pushdown-subquery branch. (check-in: [27865e316f] user: drh branch: pushdown-subquery, size: 9683) | |
| 10:27 | [45c6fa615f] part of check-in [3d5fb1ec7a] Add comments to note the name abiguity between the MySQL push-down optimization and the WHERE-clause push-down optimization. (check-in: [3d5fb1ec7a] user: drh branch: trunk, size: 7128) | |
|
2024-04-06
| ||
| 23:09 | [a3ccacdcf1] part of check-in [681dfe2dd6] Add comments to note the name abiguity between the MySQL push-down optimization and the WHERE-clause push-down optimization. (check-in: [681dfe2dd6] user: drh branch: wrong-branch, size: 9696) | |
|
2024-04-05
| ||
| 20:01 | [a8472a771f] part of check-in [2cbd7838fd] Experimental enhancement in which expressions of the form "expr IN table" can be pushed down into subexpressions. (check-in: [2cbd7838fd] user: drh branch: pushdown-IN-table, size: 8858) | |
|
2023-05-15
| ||
| 02:06 | [1495a09837] part of check-in [4902015dcf] As evidenced by forum post f3f546025a, the new RIGHT JOIN related restriction on the push-down optimization implemented by [da3fba18742b6e0b] also needs to apply to the automatic index (a.k.a. hash-join) optimization and to the Bloom filter optimization. Computation of the restriction is now moved into the sqlite3ExprIsSingleTableConstraint() routine. (check-in: [4902015dcf] user: drh branch: trunk, size: 6303) | |
|
2023-05-10
| ||
| 00:33 | [043e69055d] part of check-in [da3fba1874] New restriction on the push-down optimization to prevent an ON or USING clause on the left side of a RIGHT JOIN from being pushed down into a subquery that is on the right side of that RIGHT JOIN. Forum post a7d4be7fb6. This is similar to an earlier problem fixed at [1783655ea422185e]. Also add comments to describe previously undocumented push-down optimization restrictions. (check-in: [da3fba1874] user: drh branch: trunk, size: 5534) | |
|
2023-02-22
| ||
| 21:47 | [c183fa51f9] part of check-in [a4aacdd323] Enable the count-of-view optimization by default. Enhancement request [eaed8e36ce888f1e]. (check-in: [a4aacdd323] user: drh branch: trunk, size: 4829) | |
| 20:42 | [35c23334e5] part of check-in [aa6bd6dff7] Remove the push-down optimization restriction that was added by check-in [1ad41840c5e0fa70] because it is no longer needed after the enhancements to compound query processing in check-in [27655c9353620aa5] This resolves the performance regression reported by forum post bcc4375032. (check-in: [aa6bd6dff7] user: drh branch: trunk, size: 4294) | |
|
2022-12-14
| ||
| 14:41 | [f270b8071c] part of check-in [6ebb178c6b] If the SELECT that implements a subquery or a VIEW or a CREATE TABLE AS is a compound with different result datatypes on two or more arms of the compound, then the overall column type becomes BLOB (ANY). (check-in: [6ebb178c6b] user: drh branch: refactor-subquery-types, size: 3026) | |
| 09:06 | [149cd682ca] part of check-in [fe5a77bcc4] Back out the part of the change in [88a05141c28e5ff1] that adds affinity to the materialization of a view, as the affinity can be undefined for a compound query. This passes all TCL tests, but shows failures in the TH3 tests derived from forum post 6f842bc5b2dadcb2, presumably because the WHERE clause of the query uses constraints of the form "source_crs_code='8675'" instead of "source_crs_code=8675". Perhaps further changes on this branch should reimplement affinity on joins in cases where the affinity is unambiguous. (check-in: [fe5a77bcc4] user: drh branch: refactor-subquery-types, size: 2843) | |
|
2022-11-25
| ||
| 15:52 | [c69f0970ea] part of check-in [1ad41840c5] Add restriction (9) to the push-down optimization: If the subquery is a compound then all arms of the compound must have the same affinity. dbsqlfuzz 3a548de406a50e896c1bf7142692d35d339d697f. (check-in: [1ad41840c5] user: drh branch: trunk, size: 2711) | |
|
2017-07-19
| ||
| 18:01 | [5e72c51c5e] part of check-in [d14fc621e9] Remove some 'breakpoint' commands in test files. (check-in: [d14fc621e9] user: mistachkin branch: trunk, size: 1804) | |
|
2017-07-10
| ||
| 15:17 | [df9a5d1822] part of check-in [a4fc98113a] Fix another problem on this branch. (check-in: [a4fc98113a] user: dan branch: defer-where-subqueries, size: 1817) | |
|
2017-04-28
| ||
| 19:59 | Added: [a5d2e5e66c] part of check-in [afe68f0a80] Within a loop that uses a non-covering index test, test non-indexed terms that can be tested without seeking the main table cursor before those that cannot. (check-in: [afe68f0a80] user: dan branch: pushdown-optimization, size: 1252) | |