Why updating documents matters in MongoDB - Performance Analysis

Time Complexity: Why updating documents matters

O(n)

Understanding Time Complexity

When we update documents in MongoDB, the time it takes can change depending on how many documents we touch and what we do to them.

We want to understand how the cost of updating grows as we update more documents.

Scenario Under Consideration

Analyze the time complexity of the following code snippet.

// Update all users with age over 30 to set status to 'active'
db.users.updateMany(
  { age: { $gt: 30 } },
  { $set: { status: 'active' } }
)
    

This code updates many documents that match a condition by changing a field value.

Identify Repeating Operations

Identify the loops, recursion, array traversals that repeat.

• Primary operation: Scanning documents to find matches and updating each matched document.
• How many times: Once for each document that matches the condition (age > 30).

How Execution Grows With Input

Explain the growth pattern intuitively.

Input Size (n)	Approx. Operations
10	About 10 checks and updates if all match
100	About 100 checks and updates if all match
1000	About 1000 checks and updates if all match

Pattern observation: The work grows roughly in direct proportion to how many documents match and need updating.

Final Time Complexity

Time Complexity: O(n)

This means the time to update grows linearly with the number of documents that match the update condition.

Common Mistake

[X] Wrong: "Updating documents is always very fast and takes the same time no matter how many documents are updated."

[OK] Correct: Actually, the more documents that match the update, the more work MongoDB must do, so the time grows with the number of matched documents.

Interview Connect

Understanding how updates scale helps you explain how databases handle changes efficiently and why indexing or limiting updates matters in real projects.

Self-Check

"What if we added an index on the age field? How would the time complexity of finding documents to update change?"

Practice

1. Why is it important to update documents in MongoDB instead of deleting and inserting new ones?

easy

A. Deleting and inserting is faster and safer.

B. Updating deletes the entire document automatically.

C. Updating keeps data consistent and avoids losing other fields.

D. MongoDB does not support updating documents.

Solution

1. Step 1: Understand document update purpose

   Updating modifies only specific fields, keeping other data intact.

2. Step 2: Compare update vs delete-insert

   Deleting and inserting risks losing data and is slower than updating.

3. Final Answer:

   Updating keeps data consistent and avoids losing other fields. -> Option C

4. Quick Check:

   Update preserves data = B [OK]

Hint: Update changes fields without losing data [OK]

Common Mistakes:

• Thinking delete-insert is faster
• Believing update removes whole document
• Assuming MongoDB can't update documents

2. Which of the following is the correct syntax to update the field age to 30 in a MongoDB document?

easy

A. db.collection.updateOne({name: 'John'}, {$set: {age: 30}})

B. db.collection.updateOne({name: 'John'}, {age: 30})

C. db.collection.update({name: 'John'}, {$change: {age: 30}})

D. db.collection.updateOne({name: 'John'}, {$update: {age: 30}})

Solution

1. Step 1: Identify correct update operator

   The $set operator updates specific fields without replacing the whole document.

2. Step 2: Check syntax correctness

   Only db.collection.updateOne({name: 'John'}, {$set: {age: 30}}) uses updateOne with $set correctly.

3. Final Answer:

   db.collection.updateOne({name: 'John'}, {$set: {age: 30}}) -> Option A

4. Quick Check:

   Use $set to update fields = C [OK]

Hint: Use $set inside updateOne to change fields [OK]

Common Mistakes:

• Omitting $set operator
• Using wrong operator like $change or $update
• Passing field directly without $set

3. Given the collection documents:

{"name": "Alice", "score": 50}

What will be the result after running:

db.collection.updateOne({name: "Alice"}, {$set: {score: 75}});
db.collection.find({name: "Alice"}).toArray();

medium

A. []

B. [{"name": "Alice", "score": 75}]

C. [{"name": "Alice"}]

D. [{"name": "Alice", "score": 50}]

Solution

1. Step 1: Understand updateOne with $set

   The command changes the score field from 50 to 75 for the document where name is "Alice".

2. Step 2: Check find query result

   The find query returns the updated document with score now 75.

3. Final Answer:

   [{"name": "Alice", "score": 75}] -> Option B

4. Quick Check:

   Update changes score to 75 = D [OK]

Hint: Update changes field value, find shows updated document [OK]

Common Mistakes:

• Expecting old score after update
• Thinking update removes other fields
• Assuming update adds new document

4. What is wrong with this update command?

db.collection.updateOne({name: "Bob"}, {score: 100});

medium

A. Missing $set operator, so it replaces the whole document.

B. The filter query is incorrect syntax.

C. updateOne cannot update numeric fields.

D. The collection name is invalid.

Solution

1. Step 1: Check update command structure

   The update document must use an operator like $set to update fields without replacing the whole document.

2. Step 2: Understand effect of missing $set

   Without $set, the document is replaced entirely with {score: 100}, losing other fields.

3. Final Answer:

   Missing $set operator, so it replaces the whole document. -> Option A

4. Quick Check:

   Always use $set to update fields [OK]

Hint: Always include $set to update fields safely [OK]

Common Mistakes:

• Omitting $set and replacing document
• Thinking updateOne syntax is wrong
• Believing updateOne can't update numbers

5. You want to update the status field to "active" only if it currently exists in the document. Which update command achieves this safely without creating new fields?

hard

A. db.collection.updateMany({status: {$exists: false}}, {$set: {status: "active"}})

B. db.collection.updateMany({}, {$set: {status: "active"}})

C. db.collection.updateMany({status: null}, {$set: {status: "active"}})

D. db.collection.updateMany({status: {$exists: true}}, {$set: {status: "active"}})

Solution

1. Step 1: Use filter to check field existence

   The filter {status: {$exists: true}} selects documents where status field exists.

2. Step 2: Update only matching documents

   The $set updates status to "active" only for those documents, avoiding creating new fields.

3. Final Answer:

   db.collection.updateMany({status: {$exists: true}}, {$set: {status: "active"}}) -> Option D

4. Quick Check:

   Filter with $exists true to update safely = A [OK]

Hint: Filter with $exists:true to update only existing fields [OK]

Common Mistakes:

• Updating all documents regardless of field existence
• Using $exists:false which matches missing fields
• Filtering with null instead of $exists