> On 11/17/16, Paul wrote: > > > >> On 11/17/16, Richard Hipp wrote: > >> > On 11/17/16, Paul wrote: > >> >> That's why there was a LEFT JOIN in the first place, but as it seems, > >> >> it > >> >> wasn't that good idea. > >> > > >> > Try using CROSS JOIN instead of just JOIN or LEFT JOIN. The query > >> > planner in SQLite will not reorder a CROSS JOIN. > >> > >> But, as it turns out, if you use CROSS JOIN it goes back to sorting. > >> Bummer. > > > > Yes... unfortunately. > > > >> > >> Ok, a new optimization opportunity. > > > > So, in the upcoming releases, some of these queries may get optimised? > > The ones with the LEFT or wit the CROSS JOIN? > > > > CROSS JOIN. I don't think the LEFT JOIN case works, but I will confirm that. >
BTW, bar has a FK from foo. When FKs are on I believe SQLite can assume that constraints are not violated. Hence the right part of the LEFT JOIN can never be NULL, specifically the id. _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
