Using INNER JOIN to Combine Customer and Order Data
📖 Scenario: You work at a small online store. You have two tables: one with customer details and another with their orders. You want to see which customers placed orders and details about those orders.
🎯 Goal: Create a query using INNER JOIN to combine the customers and orders tables, showing only customers who have placed orders along with their order details.
📋 What You'll Learn
Create a customers table with columns customer_id (integer), name (text), and city (text).
Create an orders table with columns order_id (integer), customer_id (integer), and product (text).
Insert the exact data provided into both tables.
Write an INNER JOIN query to combine the tables on customer_id.
Select customers.name, customers.city, and orders.product in the result.
💡 Why This Matters
🌍 Real World
Combining customer and order data is common in sales and e-commerce to analyze who bought what.
💼 Career
Understanding INNER JOIN is essential for database querying roles like data analyst, backend developer, and database administrator.
Progress0 / 4 steps
1
Create the customers table and insert data
Create a table called customers with columns customer_id (integer), name (text), and city (text). Then insert these exact rows: (1, 'Alice', 'New York'), (2, 'Bob', 'Los Angeles'), (3, 'Charlie', 'Chicago').
MySQL
Hint
Use CREATE TABLE to define the table and INSERT INTO to add rows.
2
Create the orders table and insert data
Create a table called orders with columns order_id (integer), customer_id (integer), and product (text). Then insert these exact rows: (101, 1, 'Book'), (102, 2, 'Pen'), (103, 1, 'Notebook').
MySQL
Hint
Define the orders table with the right columns and insert the given rows.
3
Write the INNER JOIN query to combine customers and orders
Write a SELECT query that uses INNER JOIN to combine customers and orders on customer_id. Select customers.name, customers.city, and orders.product.
MySQL
Hint
Use INNER JOIN with ON customers.customer_id = orders.customer_id to combine the tables.
4
Complete the query with an ORDER BY clause
Add an ORDER BY customers.name clause at the end of the query to sort the results by customer name alphabetically.
MySQL
Hint
Use ORDER BY customers.name to sort the results alphabetically by customer name.
Practice
(1/5)
1. What does an INNER JOIN do in MySQL?
easy
A. Combines rows from two tables where matching values exist in both tables.
B. Returns all rows from the first table regardless of matches.
C. Returns all rows from the second table regardless of matches.
D. Combines rows even if there is no matching value in either table.
Solution
Step 1: Understand INNER JOIN purpose
INNER JOIN returns rows only when there is a match in both tables based on the join condition.
Step 2: Compare options with definition
Combines rows from two tables where matching values exist in both tables. correctly describes this behavior. Options A, C, and D describe other join types or incorrect behavior.
Final Answer:
Combines rows from two tables where matching values exist in both tables. -> Option A
Quick Check:
INNER JOIN = matching rows only [OK]
Hint: INNER JOIN returns only rows with matching keys in both tables [OK]
Common Mistakes:
Confusing INNER JOIN with LEFT or RIGHT JOIN
Thinking INNER JOIN returns unmatched rows
Assuming INNER JOIN returns all rows from one table
2. Which of the following is the correct syntax for an INNER JOIN in MySQL?
easy
A. SELECT * FROM table1 INNER JOIN table2 ON table1.id = table2.id;
B. SELECT * FROM table1 INNER JOIN table2 WHERE table1.id = table2.id;
C. SELECT * FROM table1 INNER JOIN table2 USING table1.id;
D. SELECT * FROM table1 INNER JOIN table2 ON table1.id == table2.id;
Solution
Step 1: Review INNER JOIN syntax
The correct syntax uses INNER JOIN with ON and a single equals sign (=) for comparison.
Step 2: Analyze each option
SELECT * FROM table1 INNER JOIN table2 ON table1.id = table2.id; uses correct syntax. SELECT * FROM table1 INNER JOIN table2 WHERE table1.id = table2.id; uses WHERE instead of ON, which is incorrect for JOIN conditions. SELECT * FROM table1 INNER JOIN table2 USING table1.id; uses USING with table prefix which is invalid; USING requires unqualified column names. SELECT * FROM table1 INNER JOIN table2 ON table1.id == table2.id; uses double equals (==) which is invalid in SQL.
Final Answer:
SELECT * FROM table1 INNER JOIN table2 ON table1.id = table2.id; -> Option A
Quick Check:
INNER JOIN syntax uses ON with = [OK]
Hint: Use ON with single = for INNER JOIN conditions [OK]
Common Mistakes:
Using WHERE instead of ON for join condition
Using double equals (==) instead of single equals (=)
Confusing USING syntax with ON syntax
3. Given two tables: Employees(id, name, dept_id) Departments(dept_id, dept_name) What will this query return?
SELECT Employees.name, Departments.dept_name FROM Employees INNER JOIN Departments ON Employees.dept_id = Departments.dept_id;
medium
A. All departments with employees, even if no employees exist.
B. All employees, even if they have no department.
C. An error because dept_id is ambiguous.
D. All employees with their department names, only if department exists.
Solution
Step 1: Understand INNER JOIN effect on these tables
The INNER JOIN returns rows where Employees.dept_id matches Departments.dept_id, so only employees with existing departments appear.
Step 2: Analyze query output
The query selects employee names and their department names only for matching dept_id pairs. Employees without a department are excluded.
Final Answer:
All employees with their department names, only if department exists. -> Option D
Quick Check:
INNER JOIN filters to matching dept_id rows [OK]
Hint: INNER JOIN shows only matching rows from both tables [OK]
Common Mistakes:
Thinking all employees appear even without departments
Confusing INNER JOIN with LEFT JOIN
Assuming ambiguous column error without aliasing
4. Identify the error in this query:
SELECT e.name, d.dept_name FROM Employees e INNER JOIN Departments d ON e.dept_id = d.id;
medium
A. Missing WHERE clause for join condition.
B. Column d.id does not exist; should be d.dept_id.
C. Alias 'e' is not allowed in INNER JOIN.
D. Using INNER JOIN without SELECT * causes error.
Solution
Step 1: Check join condition columns
The join condition uses d.id, but Departments table has dept_id column, not id.
Step 2: Identify correct column name
It should be d.dept_id to match Employees.dept_id. Other options are incorrect because aliasing is allowed, WHERE is not needed for JOIN, and SELECT * is not mandatory.
Final Answer:
Column d.id does not exist; should be d.dept_id. -> Option B
Quick Check:
Join columns must exist and match [OK]
Hint: Check column names in JOIN condition carefully [OK]
Common Mistakes:
Using wrong column names in ON clause
Thinking WHERE is required for JOIN
Believing aliases are not allowed
5. You have two tables: Orders(order_id, customer_id, amount) Customers(customer_id, name) You want to find customers who placed orders over 100 dollars. Which query correctly uses INNER JOIN to get customer names and order amounts over 100?
hard
A. SELECT Customers.name, Orders.amount FROM Orders INNER JOIN Customers ON Orders.customer_id = Customers.customer_id WHERE Orders.amount < 100;
B. SELECT Customers.name, Orders.amount FROM Customers LEFT JOIN Orders ON Customers.customer_id = Orders.customer_id WHERE Orders.amount > 100;
C. SELECT Customers.name, Orders.amount FROM Customers INNER JOIN Orders ON Customers.customer_id = Orders.customer_id WHERE Orders.amount > 100;
D. SELECT Customers.name, Orders.amount FROM Orders INNER JOIN Customers ON Orders.customer_id = Customers.customer_id WHERE Orders.amount >= 100;
Solution
Step 1: Understand the requirement
We want customers with orders over 100 dollars, so filter Orders.amount > 100.
Step 2: Check INNER JOIN usage and filter
SELECT Customers.name, Orders.amount FROM Customers INNER JOIN Orders ON Customers.customer_id = Orders.customer_id WHERE Orders.amount > 100; correctly joins Customers and Orders on customer_id and filters orders with amount > 100. SELECT Customers.name, Orders.amount FROM Customers LEFT JOIN Orders ON Customers.customer_id = Orders.customer_id WHERE Orders.amount > 100; uses LEFT JOIN instead of INNER JOIN. SELECT Customers.name, Orders.amount FROM Orders INNER JOIN Customers ON Orders.customer_id = Customers.customer_id WHERE Orders.amount >= 100; uses >= 100 which includes 100, not strictly over 100. SELECT Customers.name, Orders.amount FROM Orders INNER JOIN Customers ON Orders.customer_id = Customers.customer_id WHERE Orders.amount < 100; filters for amount < 100, opposite of requirement.
Final Answer:
SELECT Customers.name, Orders.amount FROM Customers INNER JOIN Orders ON Customers.customer_id = Orders.customer_id WHERE Orders.amount > 100; -> Option C
Quick Check:
INNER JOIN + filter amount > 100 = SELECT Customers.name, Orders.amount FROM Customers INNER JOIN Orders ON Customers.customer_id = Orders.customer_id WHERE Orders.amount > 100; [OK]
Hint: Use INNER JOIN with WHERE to filter matching rows [OK]
Common Mistakes:
Using LEFT JOIN instead of INNER JOIN
Using wrong comparison operator in WHERE
Filtering on wrong table or column
Recommended
Ready to prove it?
Pass the test and this pattern moves unknownstrongwhile earning +1 Grip toward your certificate.