MediumSQL challenge #146JOIN

Find Pairs of Employees in the Same Department

Return every pair of employees who work in the same department.

The challenge runs on the SQLabHub practice database (SQLite) and uses the employees table. You can solve it in the browser, with nothing to install.

Solve This SQL Challenge

The task

Find pairs of employees in same department.

A correct answer returns 683 rows with 2 columns: first_name, first_name.

Tables used in this challenge

employees 120 rows

id INTEGER (PK) · first_name TEXT · last_name TEXT · email TEXT · department TEXT · department_id INTEGER · title TEXT · salary REAL · hire_date TEXT · manager_id INTEGER · city TEXT · status TEXT

First 3 rows of the employees table
idfirst_namelast_nameemaildepartmentdepartment_idtitlesalaryhire_datemanager_idcitystatus
1WilliamLewiswlewis18@corp.ioCustomer Success7Senior CS Manager617742022-07-24NULLSan Diegoactive
2JohnMillerjmiller51@corp.ioLegal8Paralegal1916942021-08-09NULLSan Diegoactive
3DanielRiveradrivera50@corp.ioEngineering1VP Engineering1350672016-06-06NULLHoustonactive

The first rows of each table are shown. See how all the tables relate on the database schema page.

Expected output

Expected output of the challenge
first_namefirst_name
WilliamAmy
WilliamBarbara
WilliamCharles
WilliamDorothy
WilliamEdward

First 5 of 683 rows. This is the output of the model solution on the practice database. The task does not fix a sort order, so your rows may come back in a different order.

What you practise

  • Choosing exactly which columns a query returns
  • Combining rows from two tables on a matching key with an inner join
  • Joining a table to itself under two aliases

Hint and approach

Try the challenge first. Open these only when you need them.

Show the hint

Self join

Show the step-by-step approach

How the model solution is built, in the order the database evaluates it:

  1. Read from the employees table, under the alias e1.
  2. Join employees again, under the alias e2, on e1.department = e2.department, and only where e1.id is less than e2.id.
  3. Return only the columns e1.first_name and e2.first_name.

Model solution

Checking your session…

What to watch for

The condition e1.id < e2.id does two jobs: it stops an employee being paired with themselves and it keeps only one of (A, B) and (B, A). Using <> instead would list each pair twice.

  • Self join. Without a condition such as a.id < b.id, a self join pairs every row with itself and lists each pair twice.
  • INNER JOIN. An inner join drops rows that have no partner on the other side, and it repeats a row once for every match, which inflates SUM and COUNT.
Solve This SQL Challenge

Keep learning