Why to avoid FULL OUTER JOINS -- and what to use instead

home
database
view story

14 Kicks

Why to avoid FULL OUTER JOINS -- and what to use instead(weblogs.sqlteam.com)

submitted by jimrice14(880) 4 years, 11 months ago

Using FULL OUTER JOINS results in sloppy, inefficient SQL, with no true structure and NULLS in potentially every column in the results. Here's some better ways to write your SELECT if you think you might need to use a FULL OUTER JOIN.

2 comments |category: Database |Views: 82
Tweet

tags: Join SQL Database another

Everyones tags:

Your Tags:

Please login or signup.

Add a live kick counter to your blog >> liveImage

You can even customize the image by choosing your own colors, and then clicking the button below to update the preview and the html code:

"Kick It" text
"Kick It" background
kick count text
kick count background
border

Simply copy and paste this HTML into your blog post.

Users who kicked this story:

More who kicked this story...

Comments:

posted by yesthatmcgurk(4063) 4 years, 11 months ago 0

Good one. Glad I always stayed away from outer joins.

posted by jimrice14(880) 4 years, 11 months ago 0

>> Good one. Glad I always stayed away from outer joins.

Yikes! don't stay away from outer joins in general, stay away from FULL outer joins. LEFT OUTER JOINs are very important to understand and use when writing SQL !!!

Most Active Users

What's this?