Please help me with the following MySQL query, which joins two tables (A and B):
SELECT * from A left join B on A.sid = B.sid where (rCode = 1 Or rCode = 2 Or rCode = 3 Or rCode = 5) AND (rYear = 2011 or rYear is null)
roleCode
is a field in table A and rYear
is a field in table B
The result set is not as expected. Only 185 rows are returned, but there are 629 rows in table A that match the where condition. Shouldn't the rows without a matching row in table B be returned with null values for their B fields?
The SQL LEFT JOIN returns all rows from the left table, even if there are no matches in the right table. This means that if the ON clause matches 0 (zero) records in the right table; the join will still return a row in the result, but with NULL in each column from the right table.
The result of a join of null with any other value is null. Because null values represent unknown or inapplicable values, Transact-SQL has no basis to match one unknown value to another. You can detect the presence of null values in a column from one of the tables being joined only by using an outer join.
As we have seen from the above examples joining NULL values does not work. Even though you have two NULL values SQL Server does not treat these as the same value. Internally a value of NULL is an unknown value and therefore SQL Server does not equate an unknown value being equal to another unknown value.
In SQL Full Outer Join, all rows from both the tables are included. If there are any unmatched rows, it shows NULL values for them.
You should not specify rYear in a WHERE clause. Those limit your results after the join. You should specify rYear in an ON clause to get back records with NULL from table B.
SELECT * from A left join B on A.sid = B.sid AND (rYear = 2011 or rYear is null) where (rCode = 1 Or rCode = 2 Or rCode = 3 Or rCode = 5)
Greg, is that really all there is to the query?
Sample tables
create table A(rCode int, sid int); insert A select 1,1; insert A select 2,3; insert A select 3,2; insert A select 5,4; insert A select 1,5; create table B(rYear int, sid int); insert B select 2011,1; insert B select null,3; insert B select 2011,2; insert B select 2015,2;
Queries:
SELECT * from A left join B on A.sid = B.sid where (rCode = 1 Or rCode = 2 Or rCode = 3 Or rCode = 5) AND (rYear = 2011 or rYear is null); SELECT * from A left join B on A.sid = B.sid AND (rYear = 2011 or rYear is null) where (rCode = 1 Or rCode = 2 Or rCode = 3 Or rCode = 5);
Both of the queries are exactly the same, both returning:
rCode sid rYear sid ----------- ----------- ----------- ----------- 1 1 2011 1 2 3 NULL 3 3 2 2011 2 5 4 NULL NULL 1 5 NULL NULL
So I am surprised that Jage's query (the 2nd option) works for you but not your original. It would be different story without the inner or rYear is null
.
Think of the LEFT JOIN like this [1]
SELECT * from A left join B on A.sid = B.sid
Keep everything in A, and where matched in the ON clause, keep B otherwise pad B columns with NULL. Add the WHERE clause [2]
where (rCode = 1 Or rCode = 2 Or rCode = 3 Or rCode = 5) AND (rYear = 2011 or rYear is null);
Using the output from [1], CUT down based on the filter, applied AFTER the left join. With the rYear is null
, it should still keep all A records, on the proviso that the rCode filter is matched. However, if the filter in rYear is only
AND (rYear in (2011,2012))
It's a different story, because where B was not matched, the rYear was padded with NULL, which won't match the rYear filter -> the entire row gets removed, including the A record. Such a filter on rYear would have gone into the ON clause as shown below, otherwise might as well make it an INNER JOIN.
SELECT * from A left join B on A.sid = B.sid AND (rYear in (2011,2012)) where (rCode = 1 Or rCode = 2 Or rCode = 3 Or rCode = 5)
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With