On 23 Jan 2012, at 4:30pm, Ryan Johnson wrote: > Bump? > > On 21/01/2012 2:47 PM, Ryan Johnson wrote: >> On 21/01/2012 2:44 PM, Simon Slavin wrote: >>> On 21 Jan 2012, at 7:23pm, Ryan Johnson wrote: >>> >>>> It's a SQL89 join. Sqlite docs say SQL89 and SQL92 joins perform >>>> identically [1], which I confirmed before sending the OP. >>> Oh. Okay. If it spits out the same EXPLAIN QUERY PLAN then SQLite is >>> interpreting it the same way. >> Which brings us back to the original question: why does sqlite spit out a >> bad query plan when a vastly better one exists? There's no clear reason the >> better answer should have been hard to find.
Well, the approach would be to find a specific query, post the query and query plan, then to simplify the query until the strangeness in the query plan goes away. The last simplification is the one that caused the problem. Without that, there's no plan of attack. I don't know if Dr Hipp is pursuing this privately or expecting it to be solved collaboratively on this list. Simon. _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
