Hello Ann
Can you please explain better that phrase?
With outer joins, a condition in the WHERE clause that affects the right side
of a left outer join (the one that doesn't have to exist) effectively
turns off the outerness of the join (unless it includes OR value IS NULL).
I think this is
In general, does it make a difference whether the filter conditions are in the
JOIN or WHERE clause? In practice, I've always placed the filter conditions in
the WHERE clause and just used the ON portion of the JOIN clause to join the
tables.
We have some new members of our team with a MS
On 27/05/2014 16:17, jakef...@yahoo.com [firebird-support] wrote:
In general, does it make a difference whether the filter conditions
are in the JOIN or WHERE clause?
In particular, if there are outer joins you can get different results.
--
Tim Ward
Jake,
I've a background in MS Sql also. Had to look this up before answering,
but I don't think your new members know as much as they think they know.
In MsSql, if the sql statement is written correctly there is no consistent
gain doing it one way or the other. The optimizer sees to that.
In general, does it make a difference whether the filter conditions are in the
JOIN or WHERE clause?
In practice, I've always placed the filter conditions in the WHERE clause and
just used the ON portion of the JOIN clause to join the tables.
We have some new members of our team with a MS SQL
On Tue, May 27, 2014 at 11:17 AM, jakef...@yahoo.com [firebird-support]
firebird-support@yahoogroups.com wrote:
We have some new members of our team with a MS SQL background, and they
have a preference for including filter conditions in the JOIN clause. They
say, the predicates in the ON
