7 Commits

Author	SHA1	Message	Date
drh	ad856bbc33	Drop support for the view-scan optimization as ... it was causing multiple performance regressions. In its place, reduce the estimated row count for DISTINCT subsqueries by a factor of 8. FossilOrigin-Name: 796a65fa61373b5def9bf94e068e2dae9381a084c7e2c1e5df26929e9b07ca07	2023-09-15 20:04:31 +00:00
drh	4577b75a08	In the query planner, add a heuristic that will reduce the cost of a full ... 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: e3754cc18824aad4113ad6d81e33e5c763beb9705fc6af88d8f8c870a03c731d	2022-09-01 10:41:24 +00:00
drh	bd462bcc10	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. FossilOrigin-Name: 7153552bac51295c56a1c42ca79d57195851e232509f9e9610375692f48c7e86	2018-12-24 20:21:06 +00:00
drh	fa16f5d9d6	Enhance EXPLAIN QUERY PLAN to report the generation of constant rows using ... VALUES or just a SELECT without FROM. FossilOrigin-Name: c75eee69fa8a9b56ee58a4cc539e80cc982f43390dc3a357344d58479dd89a41	2018-05-03 01:37:13 +00:00
drh	b3f0276b9e	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. FossilOrigin-Name: 5f0e803e33aa557865d5fc830d9202d628de9a94c9757058ca48f1a560702cd3	2018-05-02 18:00:17 +00:00
dan	69b9383edf	Fix a problem causing the planner to generate sub-optimal plans for some queries ... that use recursive WITH sub-queries with LIMIT clauses. FossilOrigin-Name: 053a149cc8244a7f85137129cfcb8622efe90306	2016-12-16 15:05:40 +00:00
drh	6e7722669e	Proposed fix for an infinite loop bug in the WITH clause semantic analysis ... logic. FossilOrigin-Name: 028475cb17a4b50baf0e9aba9bd3403d0a5d03b0	2015-11-07 17:48:21 +00:00