I’m always discouraged from using one, but is there a circumstance when it’s the best approach?
Share
Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I’m always discouraged from using one, but is there a circumstance when it’s the best approach?
It’s rare, but I have a few cases where it’s used. Typically in exception reports or ETL or other very peculiar situations where both sides have data you are trying to combine.
The alternative is to use an
INNER JOIN, aLEFT JOIN(with right sideIS NULL) and aRIGHT JOIN(with left sideIS NULL) and do aUNION– sometimes this approach is better because you can customize each individual join more obviously (and add a derived column to indicate which side is found or whether it’s found in both and which one is going to win).