On Wed, Feb 27, 2019 at 9:20 PM Keith Medcalf <kmedc...@dessus.com> wrote:
> [...] As such, except in OUTER joins, you do not even have to have the ON > expression related to the table(s) which have been seen so far or even > those in the join expression ... because ON is merely a syntactic substitute for WHERE and multiple WHERE > clauses are really no more than AND conditions. The requirement for the table in an ON clause to only refer to tables > already mentioned only applies to OUTER joins ... > Are you describing a fundamental truth about SQL, or merely an implementation detail of SQLite here? Given the declarative nature of SQL, it's logical that "unseen" (when reading left-to-right) tables can still be referenced. But that's "obfuscation" IMHO, and obviously not a good idea. Joins (with equal conditions) is like "threading a needle" across tables via specific columns, and doing it "pair-wise" in "linear order" seems like a best practice to me. But I'm not expert... --DD _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
