Many hyperlinks are disabled.
Use anonymous login
to enable hyperlinks.
History for test/fts3join.test
|
2025-05-31
| ||
| 16:17 | [de31d304ba] part of check-in [1ddaa92057] Relax query flattener constraint (3b) and thereby allow flattening the RHS of a LEFT JOIN even if the RHS contains a virtual table. This was previously disallowed by [9dbae1df75219e2a] as a performance optimization. It turns out that the constraint causes performance issues, and we do not have a record of any performance issue that it solves. (check-in: [1ddaa92057] user: drh branch: trunk, size: 2854) | |
|
2023-03-03
| ||
| 21:17 | [1a4d786539] part of check-in [5a09191186] Make the SQLITE_DBCONFIG_STMT_SCANSTATUS option on by default in the CLI. (check-in: [5a09191186] user: dan branch: trunk, size: 2967) | |
|
2022-04-11
| ||
| 14:26 | [ee25def5e7] 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: 2933) | |
|
2021-03-20
| ||
| 15:11 | [b285c91955] 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: 2923) | |
|
2018-05-02
| ||
| 18:00 | [949b4f5ae3] 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: 2958) | |
|
2017-07-18
| ||
| 17:34 | [69aeb460d0] part of check-in [9dbae1df75] Do not use the flattening optimization for a sub-query on the RHS of a LEFT JOIN if that subquery reads data from a virtual table. Because it prevents the planner from creating an automatic index on the results of the sub-query, the flattening optimization sometimes slows things down in this case. (check-in: [9dbae1df75] user: dan branch: trunk, size: 2929) | |
|
2017-06-27
| ||
| 16:39 | [a758accc80] part of check-in [87b3816633] Fix a virtual table problem that can occur when the vtab is on the RHS of a LEFT JOIN and there is a MATCH constraint in the ON clause, or when the vtab is in a sub-query that is the RHS of a LEFT JOIN and there is a MATCH constraint in the WHERE clause of the sub-query. (check-in: [87b3816633] user: dan branch: trunk, size: 2310) | |
|
2016-02-05
| ||
| 16:46 | [34750f3ce1] part of check-in [a6b3527323] From test scripts, remove stray "breakpoint" commands and blank lines at the ends of files. (check-in: [a6b3527323] user: drh branch: trunk, size: 1864) | |
|
2014-01-04
| ||
| 14:42 | [53e66a0c21] part of check-in [24f84b3813] Instead of having the planner ignore plans with unusable MATCH constraints, have FTS assign extremely high costs to such plans in order to discourage the planner from using them. (check-in: [24f84b3813] user: dan branch: avoid-unusable-match, size: 1866) | |
| 14:16 | Added: [bc8e5ca3e6] part of check-in [19f3208b26] Have the planner detect cases where a MATCH constraint is applied to a virtual table, and ignore any plans that do not allow the virtual table implementation to implement the MATCH filtering. (check-in: [19f3208b26] user: dan branch: avoid-unusable-match, size: 1830) | |