I'm always discouraged from using one, but is there a circumstance when it's the best approach?
We use a FULL OUTER JOIN in Oracle when we want all unmatched data from both tables. Explanation: Oracle9i also makes it possible for you to easily execute a full outer join, including all records from the tables that would have been displayed if you had used both LEFT OUTER JOIN or RIGHT OUTER JOIN clauses.
The SQL FULL JOIN command LEFT JOIN and RIGHT JOIN each return unmatched rows from one of the tables— FULL JOIN returns unmatched rows from both tables. It is commonly used in conjunction with aggregations to understand the amount of overlap between two tables.
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
, a LEFT JOIN
(with right side IS NULL
) and a RIGHT JOIN
(with left side IS NULL
) and do a UNION
- 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).
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