On Fri, Dec 6, 2019 at 2:21 PM Richard Hipp <d...@sqlite.org> wrote: > On 12/6/19, Keith Medcalf <kmedc...@dessus.com> wrote: > > > > Perhaps the optimizer could make a "left join" that is not actually an > outer > > join into a "cross join" and preserve the nesting order ... ? > > It could do that, but that would kind of defeat the whole purpose of > the optimization, which was to free up the planner to choose a > different nesting order in cases where the LEFT JOIN didn't really matter. > > I suspect that ANALYZE might also solve the OP's problem. >
Yes it did (see below). But he also mentions that ANALYSE is slow though. Any chance there could be one day a "fast-analyse" that's less precise but still good-enough to steer the plan in the right direction? --DD On Fri, Dec 6, 2019 at 11:06 AM radovan5 <radovan.antl...@siol.net> wrote: > Yes it has and I get correct plan. Did not use analyze before [...] analyze is quite slow also [...] > _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
