Unique index behavior in MongoDB - Step-by-Step Execution

Concept Flow - Unique index behavior

Create Unique Index

↓

Insert Document

↓

Check if value exists in index

↓

Reject Insert

↓

Error: Duplicate

↓

End

When inserting a document, MongoDB checks the unique index for duplicates. If a duplicate exists, insertion is rejected with an error; otherwise, the document is added.

Execution Sample

MongoDB

db.users.createIndex({email: 1}, {unique: true});
db.users.insertOne({email: "[e-mail]"});
db.users.insertOne({email: "[e-mail]"});

Creates a unique index on 'email' and tries to insert two documents with the same email, showing the duplicate error on the second insert.

Execution Table

Step	Action	Index Check	Result	Database State
1	Create unique index on 'email'	N/A	Index created	Empty collection, index ready
2	Insert document {email: '[e-mail]'}	No duplicate found	Insert successful	Collection has 1 document with email '[e-mail]'
3	Insert document {email: '[e-mail]'}	Duplicate found	Insert rejected with duplicate key error	Collection unchanged with 1 document

💡 Insertion stops on duplicate key error at step 3

Variable Tracker

Variable	Start	After Step 1	After Step 2	After Step 3
Collection documents	[]	[]	[{email: '[e-mail]'}]	[{email: '[e-mail]'}]
Unique index on email	None	Exists	Exists	Exists

Key Moments - 2 Insights

Why does the second insert fail even though it looks like a normal insert?

Because the unique index on 'email' prevents duplicate values. The execution_table row 3 shows the duplicate check fails and insertion is rejected.

What happens to the collection after a failed insert due to unique index?

The collection remains unchanged. As shown in execution_table row 3, the document count stays the same after the failed insert.

Visual Quiz - 3 Questions

Look at the execution_table at step 2. What does the index check find?

A No duplicate found

B Duplicate found

C Index does not exist

D Index is corrupted

💡 Hint

Refer to the 'Index Check' column at step 2 in execution_table

At which step does the insertion get rejected due to a duplicate key?

A Step 1

B Step 2

C Step 3

D No rejection occurs

💡 Hint

Check the 'Result' column in execution_table for the rejection message

If the unique index was removed before step 3, what would happen?

A First insert would fail

B Second insert would succeed

C Second insert would still fail

D Both inserts would fail

💡 Hint

Look at variable_tracker showing the presence of the unique index

Concept Snapshot

Unique index in MongoDB ensures no duplicate values in indexed fields.
When inserting, MongoDB checks the index for duplicates.
If duplicate found, insertion is rejected with an error.
If no duplicate, document is added to collection.
Unique indexes help maintain data integrity by preventing duplicates.

Full Transcript

This visual execution shows how MongoDB handles unique indexes. First, a unique index is created on the 'email' field. When inserting the first document with email '[e-mail]', MongoDB checks the index and finds no duplicates, so the insert succeeds. When inserting a second document with the same email, the index check finds a duplicate, so MongoDB rejects the insert with a duplicate key error. The collection remains unchanged after the failed insert. This process ensures that no two documents have the same value in the unique indexed field, maintaining data integrity.