aboutsummaryrefslogtreecommitdiff
path: root/test/with3.test
Commit message (Collapse)AuthorAge
* The view-scan optimization was added to enhance the performance of one specificdrh2023-09-15
| | | | | | | | query, but it causes performance regressions on a host of others. Disable it (at least temporarily) in order to try to find an alternative way of fixing the one specific query that it was created to fix - an alternative way that does not cause performance problems for other unrelated queries. FossilOrigin-Name: d9625a9eafe88859c3255849ee750cc6322d5a13ddad45107f9b2085c20eff50
* When an automatic index creates a Bloom filter, show that in thedrh2023-02-28
| | | | | EXPLAIN QUERY PLAN output. FossilOrigin-Name: d7b2ac1c1a31fa4285cf6df0995db7e7705bb6a1bc94850c14c94cc4e3eb239a
* Improved comments on the new co-routine logic. Fix a C++-ism in the code.drh2022-12-08
| | | | | Update test cases to accommodate the more aggressive use of co-routines. FossilOrigin-Name: 9243e850ae656d16adc8f0e5c4dcf3dcf476312cee192c39c38685fc437ccbbd
* In the query planner, add a heuristic that will reduce the cost of a fulldrh2022-09-01
| | | | | | table scan for a materialized view or subquery if the full scan is the outer-most loop. This is shown to speed up some queries. FossilOrigin-Name: 609fbb94b8f01d6792e5941ab23ce041313d359f6788c4dde6b1ca749ab49137
* Use the canonical name, not the AS name, when showing the MATERIALIZE ordrh2021-03-20
| | | | | CO-ROUTINE lines for a CTE. FossilOrigin-Name: 1b83e232c490fe6e9f999d30399faebfac6094bf940dc21dc459ed2c97657cb2
* Revise tests cases to align with the new EXPLAIN QUERY PLAN output.drh2021-03-20
| | | FossilOrigin-Name: 50fbd532602d2c316813046ed6be8be2991c281eb5f295c4c28520a0de73862c
* Fix a problem causing spurious "<cte>: circular reference" errors to be ↵dan2021-03-18
| | | | | reported when there is actually a different error in the SQL statement. FossilOrigin-Name: 9981223618782bf867dfc8988d0c634a42f569228880c5c5e00aa4ae762cfff2
* Avoid manifesting a CTE (or other view) multiple times when it is possible todrh2021-02-13
| | | | | reuse the first manifestation. FossilOrigin-Name: 9692f510803c9b9725abb687d7c10fbc0d5ed784479ec6f3fcc55925a87fe16d
* Allow multiple recursive terms in the compound SELECT of a recursive CTE.drh2020-10-19
| | | | | | This facilitates writing a query to find find the connected components of an undirected graph. FossilOrigin-Name: 5481fa8c79c34f434e99ab633ff3d0942a309a74fb0cf38e3d3617b51d5d21dd
* Fix the VDBE so that it correctly handles the sequence of operationsdrh2020-01-18
| | | | | | OP_OpenEphemeral, OP_OpenDup, OP_OpenEphemeral, and OP_OpenDup in that order on the same cursor. FossilOrigin-Name: a1be6ee0188911448c064e2c25fb0ca1daad50f3d50fb49a34430bd09736b4a9
* Make sure the WITH stack in the Parse object is disabled following an error.drh2019-11-09
| | | FossilOrigin-Name: de6e6d6846d6a41c4821454dfdc042096234df753be08c5567b79fe535d9b6ea
* Fix a memory-leak/segfault caused by using OP_OpenDup and OP_OpenEphemeral ↵dan2019-05-03
| | | | | on the same VM cursor. FossilOrigin-Name: a9b90aa12eecdd9f2a8b2d23da8b7cac43d8b1789f5cefa3f4e939d9f2b59269
* Improvements to EXPLAIN QUERY PLAN formatting. The MULTI-INDEX OR now showsdrh2018-12-24
| | | | | | a separate "INDEX" subtree for each index. SCALAR SUBQUERY entries provide a subquery number that is related back to the .selecttrace output. FossilOrigin-Name: 7153552bac51295c56a1c42ca79d57195851e232509f9e9610375692f48c7e86
* Enhance EXPLAIN QUERY PLAN to report the generation of constant rows usingdrh2018-05-03
| | | | | VALUES or just a SELECT without FROM. FossilOrigin-Name: c75eee69fa8a9b56ee58a4cc539e80cc982f43390dc3a357344d58479dd89a41
* Fix test cases so that they work with the new EXPLAIN QUERY PLAN outputdrh2018-05-02
| | | | | | format. Only some of the cases have been fixed. This is an incremental check-in. FossilOrigin-Name: 5f0e803e33aa557865d5fc830d9202d628de9a94c9757058ca48f1a560702cd3
* Fix a problem causing the planner to generate sub-optimal plans for some queriesdan2016-12-16
| | | | | that use recursive WITH sub-queries with LIMIT clauses. FossilOrigin-Name: 053a149cc8244a7f85137129cfcb8622efe90306
* Proposed fix for an infinite loop bug in the WITH clause semantic analysisdrh2015-11-07
logic. FossilOrigin-Name: 028475cb17a4b50baf0e9aba9bd3403d0a5d03b0