Re:A Critique of SQL, 40 Years Later
by crazygringo on Wednesday August 24, 2022 @04:10PM
(#32585103)
It's not.
Assume y.a is the non-nullable primary key, while y.b is the column that may be null.
But in this example there might not be a row where y.a = 5. Or there might be. But you can't tell.
But in those cases, you can always tell by including the non-nullable key in your result set. It's already being evaluated, so it's virtually free (only adds to the network transport size).
If your database is well designed, joining on a nullable column should be a relatively exotic use case, and can be handled by writing a tiny bit more code to check for NULLs before performing your join.