Why JOINs combine related tables in MySQL - Test Your Understanding

Practice - 5 Tasks

1fill in blank

easy

Complete the code to select all columns from the employees table.

MySQL

SELECT [1] FROM employees;

Drag options to blanks, or click blank then click option'

A*

Ball

Ceverything

Dcolumns

Attempts:

3 left

💡 Hint

Common Mistakes

Writing 'all' instead of '*'

Using 'columns' which is not valid SQL syntax

The asterisk (*) means select all columns from the table.

2fill in blank

medium

Complete the code to join the employees table with the departments table on department_id.

MySQL

SELECT employees.name, departments.name FROM employees [1] departments ON employees.department_id = departments.department_id;

Drag options to blanks, or click blank then click option'

AUNION

BJOIN

CWHERE

DGROUP BY

Attempts:

3 left

💡 Hint

Common Mistakes

Using WHERE instead of JOIN for combining tables

Using UNION which combines result sets vertically

The JOIN keyword combines rows from two tables based on a related column.

3fill in blank

hard

Fix the error in the JOIN clause to correctly combine employees and departments.

MySQL

SELECT employees.name, departments.name FROM employees JOIN departments [1] employees.department_id = departments.department_id;

Drag options to blanks, or click blank then click option'

AWHERE

BUSING

CWITH

DON

Attempts:

3 left

💡 Hint

Common Mistakes

Using WHERE instead of ON in JOIN clause

Using WITH which is not valid here

The ON keyword specifies the condition for the JOIN to combine related rows.

4fill in blank

hard

Fill both blanks to select employee names and their department names using an INNER JOIN.

MySQL

SELECT employees.name AS [1], departments.name AS [2] FROM employees INNER JOIN departments ON employees.department_id = departments.department_id;

Drag options to blanks, or click blank then click option'

Aemployee_name

Bdepartment_name

Cemp_name

Ddept_name

Attempts:

3 left

💡 Hint

Common Mistakes

Using the same alias for both columns

Using unclear or confusing aliases

Aliases help rename columns in the output for clarity.

5fill in blank

hard

Fill all three blanks to create a query that selects employee names, department names, and filters for departments with 'Sales' in the name.

MySQL

SELECT employees.name AS [1], departments.name AS [2] FROM employees JOIN departments ON employees.department_id = departments.department_id WHERE departments.name [3] '%Sales%';

Drag options to blanks, or click blank then click option'

Aemp_name

Bdept_name

CLIKE

DIN

Attempts:

3 left

💡 Hint

Common Mistakes

Using IN instead of LIKE for pattern matching

Not using aliases for selected columns

The LIKE operator is used to filter text patterns in SQL.

Practice

1. Why do we use JOINs in SQL when working with multiple tables?

easy

A. To create new tables automatically

B. To delete rows from multiple tables at once

C. To combine rows from related tables based on matching columns

D. To change the data type of columns

Solution

1. Step 1: Understand the purpose of JOINs

   JOINs are used to combine rows from two or more tables based on a related column between them.

2. Step 2: Identify the correct use case

   Combining related data helps to see connected information in one result, which matches To combine rows from related tables based on matching columns.

3. Final Answer:

   To combine rows from related tables based on matching columns -> Option C

4. Quick Check:

   JOINs combine related tables = A [OK]

Hint: JOINs link tables by matching columns to combine data [OK]

Common Mistakes:

• Thinking JOINs delete or create tables
• Confusing JOINs with data type changes
• Assuming JOINs work without matching columns

2. Which of the following is the correct syntax to join two tables orders and customers on the column customer_id?

easy

A. SELECT * FROM orders JOIN customers WHER orders.customer_id = customers.customer_id;

B. SELECT * FROM orders JOIN customers ON orders.customer_id = customers.customer_id;

C. SELECT * FROM orders, customers ON orders.customer_id = customers.customer_id;

D. SELECT * FROM orders JOIN customers USING customer_id;

Solution

1. Step 1: Review JOIN syntax

   The correct JOIN syntax uses the ON clause to specify the matching columns between tables.

2. Step 2: Compare options

   SELECT * FROM orders JOIN customers ON orders.customer_id = customers.customer_id; uses JOIN with ON correctly. SELECT * FROM orders JOIN customers WHERE orders.customer_id = customers.customer_id; uses WHERE incorrectly for JOIN. SELECT * FROM orders, customers ON orders.customer_id = customers.customer_id; misuses ON without JOIN. SELECT * FROM orders JOIN customers USING customer_id; uses USING correctly and is valid syntax.

3. Final Answer:

   SELECT * FROM orders JOIN customers ON orders.customer_id = customers.customer_id; -> Option B

4. Quick Check:

   JOIN with ON clause = A [OK]

Hint: Use ON to specify join condition, not WHERE [OK]

Common Mistakes:

• Using WHERE instead of ON for JOIN condition
• Missing JOIN keyword before ON
• Confusing USING and ON syntax

3. Given these tables:
employees(id, name, dept_id)
departments(dept_id, dept_name)
What will this query return?

SELECT employees.name, departments.dept_name FROM employees JOIN departments ON employees.dept_id = departments.dept_id;

medium

A. An error because dept_id is missing

B. A list of all employees without department names

C. A list of all departments without employee names

D. A list of employee names with their department names

Solution

1. Step 1: Understand the JOIN condition

   The query joins employees and departments where dept_id matches, linking employees to their departments.

2. Step 2: Analyze the SELECT columns

   The query selects employee names and their corresponding department names, so the output shows pairs of employee and department.

3. Final Answer:

   A list of employee names with their department names -> Option D

4. Quick Check:

   JOIN on dept_id returns employee and department pairs = D [OK]

Hint: JOIN returns combined rows matching ON condition [OK]

Common Mistakes:

• Assuming JOIN returns unmatched rows
• Confusing columns in SELECT with JOIN condition
• Expecting error when columns exist

4. What is wrong with this JOIN query?

SELECT * FROM orders JOIN customers ON orders.customer_id customers.customer_id;

medium

A. Missing '=' operator in ON clause

B. Missing JOIN keyword

C. Using WHERE instead of ON

D. No tables specified

Solution

1. Step 1: Check the ON clause syntax

   The ON clause must have a condition with an operator like '=', but here it is missing between the two columns.

2. Step 2: Verify other parts

   JOIN keyword and tables are present, so the main error is the missing '=' operator.

3. Final Answer:

   Missing '=' operator in ON clause -> Option A

4. Quick Check:

   ON clause needs '=' operator = C [OK]

Hint: ON clause must have '=' between columns [OK]

Common Mistakes:

• Omitting '=' in ON condition
• Confusing ON with WHERE syntax
• Leaving out JOIN keyword

5. You have two tables:
students(id, name, class_id)
classes(class_id, class_name)
You want to list all students with their class names, but also include students without a class assigned. Which JOIN should you use?

hard

A. LEFT JOIN

B. INNER JOIN

C. RIGHT JOIN

D. CROSS JOIN

Solution

1. Step 1: Understand JOIN types

   INNER JOIN returns only matching rows. LEFT JOIN returns all rows from the left table and matching rows from the right.

2. Step 2: Apply to problem

   To include all students even if they have no class, use LEFT JOIN from students to classes.

3. Final Answer:

   LEFT JOIN -> Option A

4. Quick Check:

   Include all left table rows = LEFT JOIN = B [OK]

Hint: Use LEFT JOIN to keep all left table rows [OK]

Common Mistakes:

• Using INNER JOIN excludes unmatched rows
• RIGHT JOIN keeps right table rows, not left
• CROSS JOIN creates all combinations, not related rows