Why Unique indexes in MySQL? - Purpose & Use Cases

The Big Idea

What if your database could instantly stop duplicates before they cause trouble?

The Scenario

Imagine you have a list of email addresses stored in a simple spreadsheet. You want to make sure no email is entered twice, but you have to check each new entry manually by scanning the entire list every time.

The Problem

This manual checking is slow and tiring. It's easy to miss duplicates, especially as the list grows. Mistakes can cause confusion, lost messages, or even security problems if two users share the same email by accident.

The Solution

Unique indexes automatically stop duplicates from being saved in your database. They act like a smart gatekeeper that checks every new entry and only allows it if it's truly unique, saving you time and avoiding errors.

Before vs After

✗ Before

Check each new email by scanning the whole list before adding it.

✓ After

CREATE UNIQUE INDEX idx_email ON users(email);

What It Enables

It lets your database keep data clean and reliable without extra work from you.

Real Life Example

When signing up for a website, unique indexes ensure no two users can register with the same email address, preventing account mix-ups.

Key Takeaways

Manual duplicate checks are slow and error-prone.

Unique indexes automatically prevent duplicate data entries.

This keeps your data accurate and your applications reliable.

Practice

1. What is the main purpose of a UNIQUE index in MySQL?

easy

A. To prevent duplicate values in one or more columns

B. To speed up data insertion

C. To allow duplicate values in a column

D. To delete duplicate rows automatically

Solution

1. Step 1: Understand the role of UNIQUE index

   A UNIQUE index ensures that no two rows have the same value in the indexed column(s).

2. Step 2: Compare options with this definition

   Only To prevent duplicate values in one or more columns correctly states that UNIQUE prevents duplicates. Others are incorrect or unrelated.

3. Final Answer:

   To prevent duplicate values in one or more columns -> Option A

4. Quick Check:

   UNIQUE index = prevent duplicates [OK]

Hint: UNIQUE means no duplicates allowed in indexed columns [OK]

Common Mistakes:

• Thinking UNIQUE speeds up inserts
• Believing UNIQUE allows duplicates
• Confusing UNIQUE with automatic deletion

2. Which of the following is the correct syntax to create a UNIQUE index on the column email in a table named users?

easy

A. CREATE UNIQUE KEY idx_email FROM users(email);

B. CREATE INDEX UNIQUE idx_email ON users(email);

C. CREATE UNIQUE INDEX idx_email ON users(email);

D. CREATE UNIQUE ON users INDEX idx_email(email);

Solution

1. Step 1: Recall correct syntax for UNIQUE index creation

   The correct syntax is: CREATE UNIQUE INDEX index_name ON table_name(column_name);

2. Step 2: Match options with correct syntax

   CREATE UNIQUE INDEX idx_email ON users(email); matches exactly. Others have wrong keyword order or syntax errors.

3. Final Answer:

   CREATE UNIQUE INDEX idx_email ON users(email); -> Option C

4. Quick Check:

   CREATE UNIQUE INDEX ... ON ... (column) [OK]

Hint: Remember: CREATE UNIQUE INDEX name ON table(column) [OK]

Common Mistakes:

• Swapping UNIQUE and INDEX keywords
• Using FROM instead of ON
• Incorrect keyword order

3. Given the table employees with a UNIQUE index on employee_id, what happens if you run this query?

INSERT INTO employees (employee_id, name) VALUES (101, 'Alice');
INSERT INTO employees (employee_id, name) VALUES (101, 'Bob');

medium

A. The second insert fails with a duplicate key error

B. Both rows are inserted successfully

C. The second insert overwrites the first row

D. The second insert is ignored silently

Solution

1. Step 1: Understand UNIQUE index effect on inserts

   A UNIQUE index on employee_id prevents duplicate values in that column.

2. Step 2: Analyze the inserts

   The first insert adds employee_id 101. The second insert tries to add the same employee_id 101, violating the UNIQUE constraint, causing an error.

3. Final Answer:

   The second insert fails with a duplicate key error -> Option A

4. Quick Check:

   UNIQUE index blocks duplicate inserts [OK]

Hint: Duplicate insert on UNIQUE column causes error [OK]

Common Mistakes:

• Assuming duplicates are allowed
• Thinking second insert overwrites first
• Believing second insert is ignored silently

4. You tried to create a UNIQUE index on the column username but got an error. Which of these is the most likely cause?

medium

A. The table does not exist

B. The username column contains duplicate values

C. You forgot to specify the index name

D. UNIQUE indexes are not supported on text columns

Solution

1. Step 1: Understand UNIQUE index creation requirements

   Creating a UNIQUE index requires all existing values in the column to be unique.

2. Step 2: Identify common error causes

   If duplicates exist, MySQL throws an error when creating the UNIQUE index.

3. Final Answer:

   The username column contains duplicate values -> Option B

4. Quick Check:

   Duplicates block UNIQUE index creation [OK]

Hint: Check for duplicates before creating UNIQUE index [OK]

Common Mistakes:

• Assuming index name is mandatory
• Believing UNIQUE not allowed on text columns
• Ignoring existing duplicates

5. You want to ensure that the combination of first_name and last_name in the contacts table is unique, but duplicates are still appearing. Which is the best way to fix this?

hard

A. Use a CHECK constraint to prevent duplicates

B. Create separate UNIQUE indexes on first_name and last_name individually

C. Add a PRIMARY KEY on first_name

D. Create a UNIQUE index on both first_name and last_name columns together

Solution

1. Step 1: Understand uniqueness on multiple columns

   To ensure uniqueness on a combination, a composite UNIQUE index on both columns is needed.

2. Step 2: Analyze other options

   Separate UNIQUE indexes allow duplicates across combinations. PRIMARY KEY on one column doesn't cover both. CHECK constraints can't enforce uniqueness.

3. Final Answer:

   Create a UNIQUE index on both first_name and last_name columns together -> Option D

4. Quick Check:

   Composite UNIQUE index = unique pairs [OK]

Hint: Use composite UNIQUE index for multi-column uniqueness [OK]

Common Mistakes:

• Creating separate UNIQUE indexes instead of composite
• Using PRIMARY KEY on one column only
• Relying on CHECK constraints for uniqueness