Table aliases in MySQL - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ query_result

intermediate

Output of query using table aliases

Given two tables employees and departments, what is the output of this query?

SELECT e.name, d.name FROM employees AS e JOIN departments AS d ON e.dept_id = d.id;

MySQL

CREATE TABLE employees (id INT, name VARCHAR(20), dept_id INT);
INSERT INTO employees VALUES (1, 'Alice', 10), (2, 'Bob', 20);
CREATE TABLE departments (id INT, name VARCHAR(20));
INSERT INTO departments VALUES (10, 'HR'), (20, 'Sales');

SELECT e.name, d.name FROM employees AS e JOIN departments AS d ON e.dept_id = d.id;

A [{"name": "Alice"}, {"name": "Bob"}]

B [{"name": "Alice", "name": "Sales"}, {"name": "Bob", "name": "HR"}]

C [{"employee_name": "Alice", "department_name": "HR"}, {"employee_name": "Bob", "department_name": "Sales"}]

D SyntaxError

💡 Hint

Look at how the aliases e and d refer to employees and departments tables.

The query joins employees (aliased as e) with departments (aliased as d) on matching dept_id and id. So Alice is in HR and Bob is in Sales.

📝 Syntax

intermediate

Identify the syntax error with table alias

Which option contains a syntax error when using table aliases in MySQL?

MySQL

SELECT e.name FROM employees e JOIN departments d ON e.dept_id = d.id;

A SELECT e.name FROM employees AS e departments AS d ON e.dept_id = d.id;

B SELECT e.name FROM employees AS e JOIN departments AS d ON e.dept_id = d.id;

C SELECT e.name FROM employees e JOIN departments d ON e.dept_id = d.id;

D SELECT e.name FROM employees e, departments d WHERE e.dept_id = d.id;

💡 Hint

Check if the JOIN keyword is missing or misplaced.

Option A misses the JOIN keyword between the two table aliases, causing a syntax error.

❓ optimization

advanced

Optimizing query with table aliases

Which option uses table aliases to make the query more readable and efficient?

MySQL

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

A SELECT e.name, d.name FROM employees e JOIN departments d ON e.dept_id = d.id;

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

C SELECT e.name, d.name FROM employees JOIN departments ON employees.dept_id = departments.id;

D SELECT e.name, d.name FROM employees e, departments d WHERE employees.dept_id = departments.id;

💡 Hint

Using aliases shortens table names and clarifies columns.

Option A uses aliases e and d consistently, making the query shorter and clearer.

🔧 Debug

advanced

Debug the ambiguous column error

What error will this query raise?

SELECT name FROM employees e JOIN departments d ON e.dept_id = d.id;

MySQL

CREATE TABLE employees (id INT, name VARCHAR(20), dept_id INT);
CREATE TABLE departments (id INT, name VARCHAR(20));

SELECT name FROM employees e JOIN departments d ON e.dept_id = d.id;

A Syntax error

B Ambiguous column name 'name' error

C No error, returns employee names

D No error, returns department names

💡 Hint

Both tables have a column named 'name'.

The query does not specify which 'name' column to select, causing ambiguity error.

🧠 Conceptual

expert

Purpose of table aliases in complex queries

Why are table aliases especially useful in queries involving the same table multiple times?

A They prevent SQL injection attacks.

B They improve database performance by caching table data.

C They automatically create indexes on the tables.

D They allow referencing the same table multiple times with different names to compare rows.

💡 Hint

Think about self-joins and comparing rows within the same table.

Aliases let you treat the same table as if it were two different tables, useful for self-joins.

Practice

1. What is the main purpose of using table aliases in a SQL query?

easy

A. To delete a table after the query runs

B. To give a short name to a table for easier reference

C. To create a new table from an existing one

D. To rename columns permanently in the database

Solution

1. Step 1: Understand what table aliases do

   Table aliases provide a temporary short name for a table within a query.

2. Step 2: Compare options with this purpose

   Only To give a short name to a table for easier reference correctly describes this purpose; others describe unrelated actions.

3. Final Answer:

   To give a short name to a table for easier reference -> Option B

4. Quick Check:

   Table aliases = short table names [OK]

Hint: Aliases shorten table names to simplify queries [OK]

Common Mistakes:

• Thinking aliases rename tables permanently
• Confusing aliases with creating or deleting tables
• Using aliases only for columns

2. Which of the following is the correct syntax to assign an alias c to a table named customers in a SELECT query?

easy

A. SELECT * FROM customers c c;

B. SELECT * FROM customers c AS;

C. SELECT * FROM AS customers c;

D. SELECT * FROM customers AS c;

Solution

1. Step 1: Recall correct alias syntax

   The correct syntax is: FROM table_name AS alias or FROM table_name alias.

2. Step 2: Check each option

   SELECT * FROM customers AS c; uses 'AS' correctly. Options B, C, and D have syntax errors or misplaced keywords.

3. Final Answer:

   SELECT * FROM customers AS c; -> Option D

4. Quick Check:

   Correct alias syntax = SELECT * FROM customers AS c; [OK]

Hint: Use 'AS' between table name and alias or just space [OK]

Common Mistakes:

• Placing 'AS' after alias name
• Using multiple aliases for one table
• Misordering keywords in FROM clause

3. Given the tables orders and customers, what will the following query return?

SELECT c.name, o.order_id FROM customers AS c JOIN orders AS o ON c.id = o.customer_id;

medium

A. A list of customer names with their order IDs

B. A list of order IDs only

C. A list of customer names only

D. An error due to incorrect alias usage

Solution

1. Step 1: Understand the query structure

   The query joins customers (aliased as c) and orders (aliased as o) on matching IDs.

2. Step 2: Analyze the SELECT clause

   It selects customer names (c.name) and order IDs (o.order_id), so both appear in results.

3. Final Answer:

   A list of customer names with their order IDs -> Option A

4. Quick Check:

   Join with aliases returns combined columns [OK]

Hint: Aliases let you select columns clearly from joined tables [OK]

Common Mistakes:

• Assuming aliases cause errors
• Expecting only one column in output
• Ignoring join condition effects

4. Identify the error in this query using table aliases:

SELECT c.name, o.order_id FROM customers c JOIN orders o ON c.id = orders.customer_id;

medium

A. Missing AS keyword for aliases

B. Aliases cannot be used in JOIN clauses

C. Using 'orders' instead of alias 'o' in ON clause

D. SELECT clause must use full table names

Solution

1. Step 1: Check alias usage in JOIN condition

   The query aliases 'orders' as 'o', but ON clause uses 'orders.customer_id' instead of 'o.customer_id'.

2. Step 2: Understand alias consistency

   Once aliased, the original table name should not be used in the query; use the alias instead.

3. Final Answer:

   Using 'orders' instead of alias 'o' in ON clause -> Option C

4. Quick Check:

   Use aliases consistently after defining them [OK]

Hint: Use alias names everywhere after aliasing tables [OK]

Common Mistakes:

• Mixing original table names with aliases
• Thinking AS keyword is mandatory
• Assuming aliases can't be used in JOIN

5. You want to join the employees table to itself to find pairs of employees who share the same manager. Which query correctly uses table aliases to achieve this?

hard

A. SELECT e1.name, e2.name FROM employees AS e1 JOIN employees AS e2 ON e1.manager_id = e2.manager_id WHERE e1.id != e2.id;

B. SELECT employees.name, employees.name FROM employees JOIN employees ON employees.manager_id = employees.manager_id;

C. SELECT e.name FROM employees e JOIN employees e ON e.manager_id = e.manager_id;

D. SELECT e1.name, e2.name FROM employees e1 JOIN employees e2 ON e1.id = e2.id;

Solution

1. Step 1: Understand self-join with aliases

   Joining a table to itself requires different aliases to distinguish rows.

2. Step 2: Check join condition and alias usage

   SELECT e1.name, e2.name FROM employees AS e1 JOIN employees AS e2 ON e1.manager_id = e2.manager_id WHERE e1.id != e2.id; correctly uses aliases e1 and e2 and joins on matching manager_id, excluding same employee pairs.

3. Step 3: Review other options for errors

   SELECT employees.name, employees.name FROM employees JOIN employees ON employees.manager_id = employees.manager_id; uses same table names without aliases, causing ambiguity. SELECT e.name FROM employees e JOIN employees e ON e.manager_id = e.manager_id; uses same alias twice, invalid syntax. SELECT e1.name, e2.name FROM employees e1 JOIN employees e2 ON e1.id = e2.id; joins on employee IDs, not managers.

4. Final Answer:

   SELECT e1.name, e2.name FROM employees AS e1 JOIN employees AS e2 ON e1.manager_id = e2.manager_id WHERE e1.id != e2.id; -> Option A

5. Quick Check:

   Self-join needs distinct aliases and correct join condition [OK]

Hint: Use different aliases for self-join tables [OK]

Common Mistakes:

• Using same alias for both tables
• Joining on wrong columns
• Not excluding same row pairs in self-join