Wow. I've seen some odd behavior in SQL before, but this one seems to defy logic. Maybe I'm missing something obvious.
It hinges on a fairly simple logic statement: Given that a record exists in one table, then a matching record either exists in another table or it does not exist in that...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.