> > What is the rationale about placing complex conditions in the ON part
> > of an inner join rather than in an WHERE clause?
>
>Except for outer joins, the difference is purely stylistic. They are
>functionally equivalent. In fact, SQLite internally rewrites the
>former to the latter, before
On Tue, Jul 20, 2010 at 9:43 AM, Jean-Christophe Deschamps
wrote:
> What is the rationale about placing complex conditions in the ON part
> of an inner join rather than in an WHERE clause?
My sense is that it is not so much about "complexity" but more about
the logic of the
Jean-Christophe Deschamps wrote:
> What is the rationale about placing complex conditions in the ON part
> of an inner join rather than in an WHERE clause?
Except for outer joins, the difference is purely stylistic. They are
functionally equivalent. In fact, SQLite internally
What is the rationale about placing complex conditions in the ON part
of an inner join rather than in an WHERE clause?
I understand that the ON clause will limit the temporary table
processed by a subsequent WHERE clause, while a larger table will be
filtered by the WHERE part if no selective
4 matches
Mail list logo