On 16 Oct 2016, at 7:17pm, Jens Alfke <j...@mooseyard.com> wrote:

> I didn’t think a view had a physical manifestation that had to be built; I 
> thought it was just a shortcut/macro for a nested SELECT statement.
> Or is the query optimizer not able to convert the nested SELECT into the same 
> form as the first query?

The query optimizer cannot flatten all sub-SELECTs.  It always understands JOIN 
but the analysis needed for every possible SELECT combination is too much.

To figure out what it's doing use EXPLAIN QUERY PLAN.

sqlite-users mailing list

Reply via email to