• For this video, we use a self join table since our join will only involve one table. Since we join the table onto itself, any column that we use in the join condition will match provided that we don’t change any part of the condition (which we do in our example and I show why).
  • As a quick reminder, not all SQL languages may support the exact syntax shown. Different SQL languages may have different approaches to solving the same problem or developing the same solution.
  • As we see with the results of the INNER JOIN, what output issue occurs when we join Table1 and Table2 when it comes to columns? For developers with application experience, what would be the issue here? Keep in mind that with INNER JOINs, this is seldom an issue, but worth considering in this case because it does come up.
  • How does a LEFT SEMI JOIN solve the above issue?
  • When would we consider using a LEFT SEMI JOIN? What could be the possible issue?




Data | Development | Security.

Love podcasts or audiobooks? Learn on the go with our new app.

Recommended from Medium

Define a Test Strategy for Your Project

Languages in Programming

MoonBot Presale & Launch

Social Groups: The Flip Side to Conway’s Law


Unsupervised Translation of Programming Languages

Codeigniter VS Laravel

Lets create a java sample project part 1

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store
SQLInSix Minutes

SQLInSix Minutes

Data | Development | Security.

More from Medium

SQL Query optimizer


What is PL/SQL? Why use PL/SQL over SQL.

DDL and DML in the database