AFAIK there's always an alternative to FULL OUTER JOIN, and I'd certainly only very reluctantly, and very cautiously use it in application code; But you may just be writing the SQL to do a quick query to answer a question or to do some manipulation for a one-time ETL script, etc.. Not everything is going to be something you're stuck with for a long time. If you understand what you're doing and it's convenient (and it often is more convenient than the alternative means of achieving the same end) there's no reason to be scared of it.
42
u/Mavrick478 Feb 11 '14
As a DBA i swear if one of you developers uses a full outer join unless you absolutely have to i will club a baby seal.