Table aliases in MySQL

Introduction

Table aliases let you give a short name to a table in a query. This makes writing and reading queries easier, especially when using multiple tables.

When you join two or more tables and want to write shorter names.

When a table name is long and you want to type less.

When the same table is used twice in a query and needs different names.

When you want to make your query clearer by using meaningful short names.

Syntax

MySQL

SELECT column_name(s) FROM table_name AS alias_name;

The keyword AS is optional. You can write: FROM table_name alias_name

Alias names only exist during the query execution and do not change the actual table name.

Examples

Here, 'customers' table is given the alias 'c'. We select the 'name' column using 'c'.

MySQL

SELECT c.name FROM customers AS c;

Two tables 'orders' and 'customers' are aliased as 'o' and 'c' to shorten the query.

MySQL

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

The same table 'employees' is used twice with aliases 'e1' and 'e2' to compare employees and their managers.

MySQL

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

Sample Program

We create a simple 'customers' table and insert two rows. Then we select all customers using the alias 'c'.

MySQL

CREATE TABLE customers (id INT, name VARCHAR(20));
INSERT INTO customers VALUES (1, 'Alice'), (2, 'Bob');

SELECT c.id, c.name FROM customers AS c;

Important Notes

Aliases help avoid confusion when joining tables with similar column names.

Always use meaningful alias names to keep queries readable.

You cannot use aliases outside the query where they are defined.

Summary

Table aliases give short names to tables in queries.

They make queries easier to write and read.

Aliases are especially useful when joining multiple tables or the same table twice.

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