Actually, SQLite implements JOIN USING by translating the USING clausing into some extra WHERE clause terms. It does the same with NATURAL JOIN and JOIN ON. So while those constructs might be helpful to the human reader, they don't really make any difference to SQLite's query optimizer.
Thanks for the specifics, very good to know.
My suggestion was based on the idea that, while it may be equivalent now, you could roll out a new version tomorrow with optimizations for JOINS. It is far less likely to roll out a new optimizer that would catch convolutions of where clauses that could be optimized. The latter would be more universally useful, but immensely harder to write, I expect.
thanks again.
michael
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
