UNIQUE constraints in MySQL - Time & Space Complexity

Time Complexity: UNIQUE constraints

O(n)

Understanding Time Complexity

When we use UNIQUE constraints in a database, the system must check if a value already exists before adding a new one.

We want to understand how the time to check grows as the data grows.

Scenario Under Consideration

Analyze the time complexity of enforcing a UNIQUE constraint during an INSERT.

INSERT INTO users (email) VALUES ('[e-mail]');
-- The database checks if '[e-mail]' already exists in the email column
-- If it does, the insert fails; if not, it adds the new row
    

This code tries to add a new email, and the database must ensure no duplicate emails exist.

Identify Repeating Operations

The database must check existing rows to enforce uniqueness.

• Primary operation: Searching for the value in the column with the UNIQUE constraint.
• How many times: Once per insert, but the search may scan many rows depending on data size.

How Execution Grows With Input

As the number of rows grows, the time to check for duplicates can grow too.

Input Size (n)	Approx. Operations
10	About 10 checks
100	About 100 checks
1000	About 1000 checks

Pattern observation: Without special help, the checks grow roughly in direct proportion to the number of rows.

Final Time Complexity

Time Complexity: O(n)

This means the time to check for duplicates grows roughly in step with the number of rows in the table.

Common Mistake

[X] Wrong: "Checking for duplicates is always instant no matter how big the table is."

[OK] Correct: Without an index, the database must look through many rows, so more data means more work.

Interview Connect

Understanding how UNIQUE constraints affect performance helps you design better databases and write efficient queries.

Self-Check

What if the UNIQUE constraint had an index supporting it? How would the time complexity change?

Practice

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

easy

A. To prevent duplicate values in a column or set of columns

B. To allow NULL values in a column

C. To speed up query performance

D. To automatically generate unique IDs

Solution

1. Step 1: Understand the role of UNIQUE constraint

   A UNIQUE constraint ensures that all values in a column or a group of columns are different from each other.

2. Step 2: Compare with other options

   Options A, C, and D describe other features: allowing NULLs, indexing, and auto-increment, which are not the main purpose of UNIQUE.

3. Final Answer:

   To prevent duplicate values in a column or set of columns -> Option A

4. Quick Check:

   UNIQUE constraint = prevent duplicates [OK]

Hint: UNIQUE means no two rows share the same value [OK]

Common Mistakes:

• Confusing UNIQUE with PRIMARY KEY
• Thinking UNIQUE allows duplicates
• Assuming UNIQUE speeds up queries

2. Which of the following is the correct syntax to add a UNIQUE constraint to an existing column email in a table users?

easy

A. ALTER TABLE users SET UNIQUE email;

B. ALTER TABLE users ADD UNIQUE (email);

C. ALTER TABLE users ADD UNIQUE email;

D. ALTER TABLE users ADD CONSTRAINT UNIQUE email;

Solution

1. Step 1: Recall correct ALTER TABLE syntax for UNIQUE

   The correct syntax is to use ADD UNIQUE (column_name) inside ALTER TABLE.

2. Step 2: Check each option

   ALTER TABLE users ADD UNIQUE (email); matches the correct syntax. Options A, B, and C are invalid or incomplete syntax.

3. Final Answer:

   ALTER TABLE users ADD UNIQUE (email); -> Option B

4. Quick Check:

   ALTER TABLE ADD UNIQUE (column) [OK]

Hint: Use ADD UNIQUE (column) to add constraint [OK]

Common Mistakes:

• Omitting parentheses around column name
• Using SET UNIQUE which is invalid
• Missing ADD keyword

3. Given the table users(id INT, username VARCHAR(50), email VARCHAR(100)) with a UNIQUE constraint on email, what happens if you run this query twice?

INSERT INTO users (id, username, email) VALUES (1, 'alice', '[e-mail]');

medium

A. Both inserts succeed, creating two identical rows

B. Both inserts fail due to UNIQUE constraint

C. Second insert updates the existing row

D. First insert succeeds, second insert fails with duplicate error

Solution

1. Step 1: Understand UNIQUE constraint effect on inserts

   The UNIQUE constraint on email prevents duplicate emails. The first insert adds the row successfully.

2. Step 2: Analyze second insert behavior

   The second insert tries to add the same email again, violating the UNIQUE constraint, causing an error.

3. Final Answer:

   First insert succeeds, second insert fails with duplicate error -> Option D

4. Quick Check:

   UNIQUE blocks duplicate inserts [OK]

Hint: Duplicate insert fails due to UNIQUE constraint [OK]

Common Mistakes:

• Assuming duplicates are allowed
• Thinking second insert updates existing row
• Confusing UNIQUE with PRIMARY KEY behavior

4. You have this table creation statement:

CREATE TABLE products (id INT, code VARCHAR(20) UNIQUE);

You try to insert two rows:

INSERT INTO products VALUES (1, 'X123');
INSERT INTO products VALUES (2, 'X123');

But the second insert fails. What is the most likely cause?

medium

A. The UNIQUE constraint on code prevents duplicate values

B. The id column is missing a PRIMARY KEY

C. The table does not allow NULL values in code

D. The syntax of the INSERT statement is incorrect

Solution

1. Step 1: Identify the UNIQUE constraint effect

   The code column has a UNIQUE constraint, so duplicate values like 'X123' are not allowed.

2. Step 2: Analyze the insert failure reason

   The second insert tries to add 'X123' again, violating the UNIQUE constraint, causing failure.

3. Final Answer:

   The UNIQUE constraint on code prevents duplicate values -> Option A

4. Quick Check:

   UNIQUE constraint blocks duplicate column values [OK]

Hint: UNIQUE blocks duplicate values in that column [OK]

Common Mistakes:

• Thinking PRIMARY KEY is required for uniqueness
• Assuming NULL disallows duplicates
• Blaming syntax error for insert failure

5. You want to ensure that the combination of first_name and last_name in a contacts table is unique, but each column alone can have duplicates. Which is the correct way to enforce this in MySQL?

hard

A. Add a PRIMARY KEY on first_name

B. Add UNIQUE constraints separately on first_name and last_name

C. Add a UNIQUE constraint on (first_name, last_name) together

D. Add a UNIQUE constraint only on last_name

Solution

1. Step 1: Understand composite UNIQUE constraints

   A UNIQUE constraint on multiple columns ensures the combination is unique, but allows duplicates in each column individually.

2. Step 2: Evaluate options for enforcing uniqueness

   Add a UNIQUE constraint on (first_name, last_name) together correctly adds a UNIQUE constraint on the pair (first_name, last_name). Options B, C, and D enforce uniqueness incorrectly or partially.

3. Final Answer:

   Add a UNIQUE constraint on (first_name, last_name) together -> Option C

4. Quick Check:

   Composite UNIQUE = unique pairs, not individual columns [OK]

Hint: Use UNIQUE on multiple columns for combined uniqueness [OK]

Common Mistakes:

• Adding UNIQUE on each column separately
• Confusing PRIMARY KEY with UNIQUE
• Not using composite constraint for pairs