7 Commits

Author	SHA1	Message	Date
drh	aa0ba4345d	Fix the query planner so that when it has a choice of full-scan tables to ... move to the outer loop, it chooses the one that is likely to give the fewest output rows. FossilOrigin-Name: 309bbedf9648c750d7b8aedbc15d4fd68f846824	2010-08-05 02:52:32 +00:00
drh	5e377d90ed	If the outer loop of a join must be a full table scan, make sure that an ... incomplete ANALYZE does not trick the planner into use a table that might be indexable in an inner loop. Ticket [13f033c865f878] FossilOrigin-Name: e7a714b52c45af096af74049826d32c647abfe3f	2010-08-04 21:17:16 +00:00
drh	ed754ce2cc	Further refinements to table order selection on join query planning. ... FossilOrigin-Name: defaf0d99a807027f8883bf821b6482025f9f54e	2010-04-15 01:04:54 +00:00
drh	dafc0ce818	Additional work on ticket #3015. The previous fix (check-in (4919)) did ... not appear to work in all cases and it disabled indexing in some places where it should not have. New test cases added to help insure that the current fix is better. (CVS 5026) FossilOrigin-Name: 0d2e258e1a3276e55903ba2ded987f8d8a18cacd	2008-04-17 19:14:02 +00:00
drh	61dfc31d80	Query optimizer enhancement: In "FROM a,b,c left join d" allow the C table ... to be reordered with A and B. This used to be the case but the capability was removed by (3203) and (3052) in response to ticket #1652. This change restores the capability. (CVS 3529) FossilOrigin-Name: 7393c81b8cb9d4344ae744de9eabcb3af64f1db8	2006-12-16 16:25:15 +00:00
drh	df26fd5edd	In joins of the form "A left B, C" make sure they are not transformed into ... "A left C, B". Ticket #1830. See also #1652. (CVS 3203) FossilOrigin-Name: 2baa983653796e16d36739e37b0be1672bf59a92	2006-06-06 11:45:54 +00:00
drh	570b935c2a	In joins of the form: "A, B left C" make sure that the reordering optimization ... does not put table A after table C. Ticket #1652. (CVS 3052) FossilOrigin-Name: 248b9be93d9532e31c640432b75c3310e180acb3	2006-02-01 02:45:02 +00:00