Upsert behavior (update or insert) in MongoDB - Time & Space Complexity

Time Complexity: Upsert behavior (update or insert)

O(log n)

Understanding Time Complexity

When using upsert in MongoDB, we want to know how the time to complete the operation changes as the data grows.

We ask: How does MongoDB find and update or insert a document as the collection gets bigger?

Scenario Under Consideration

Analyze the time complexity of the following code snippet.

db.collection.updateOne(
  { _id: 123 },
  { $set: { name: "Alice" } },
  { upsert: true }
)
    

This code tries to find a document with _id 123. If found, it updates the name. If not, it inserts a new document with _id 123 and name "Alice".

Identify Repeating Operations

Identify the loops, recursion, array traversals that repeat.

• Primary operation: Searching the collection for a document matching the filter {_id: 123}.
• How many times: This search happens once per upsert operation.

How Execution Grows With Input

As the collection grows, finding the document can take longer if there is no index on _id.

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

Pattern observation: Without an index, the search grows linearly with the number of documents. With an index, the search is much faster and does not grow linearly.

Final Time Complexity

Time Complexity: O(log n)

This means the time to find and update or insert a document grows slowly as the collection grows, thanks to indexing.

Common Mistake

[X] Wrong: "Upsert always takes the same time no matter how big the collection is."

[OK] Correct: The time depends on how MongoDB finds the document. Without an index, it checks many documents, so it takes longer as the collection grows.

Interview Connect

Understanding how upsert works and its time cost helps you explain database efficiency clearly and confidently in real-world situations.

Self-Check

"What if we removed the index on _id? How would the time complexity of the upsert change?"

Practice

1. What does the upsert option do in a MongoDB updateOne operation?

easy

A. It only inserts a new document without updating existing ones.

B. It updates a document if it exists, or inserts a new one if it does not.

C. It deletes a document if it exists, otherwise does nothing.

D. It duplicates the document regardless of existence.

Solution

1. Step 1: Understand the upsert option

   The upsert option in MongoDB means update if found, insert if not found.

2. Step 2: Apply to updateOne operation

   When using updateOne with upsert: true, MongoDB updates the matching document or inserts a new one if none matches.

3. Final Answer:

   It updates a document if it exists, or inserts a new one if it does not. -> Option B

4. Quick Check:

   Upsert = update or insert [OK]

Hint: Upsert means update if found, else insert new [OK]

Common Mistakes:

• Thinking upsert only inserts without updating
• Confusing upsert with delete operation
• Assuming upsert duplicates documents

2. Which of the following is the correct syntax to perform an upsert using updateOne in MongoDB?

easy

A. db.collection.updateOne(filter, update, {update: true})

B. db.collection.updateOne(filter, update, {insert: true})

C. db.collection.updateOne(filter, update, {upsert: true})

D. db.collection.updateOne(filter, update, {replace: true})

Solution

1. Step 1: Recall the updateOne method parameters

   The updateOne method takes a filter, an update document, and an options object.

2. Step 2: Identify the correct option for upsert

   The option to enable upsert is {upsert: true}, which tells MongoDB to insert if no match is found.

3. Final Answer:

   db.collection.updateOne(filter, update, {upsert: true}) -> Option C

4. Quick Check:

   Use upsert: true in options [OK]

Hint: Use {upsert: true} in updateOne options [OK]

Common Mistakes:

• Using {insert: true} instead of {upsert: true}
• Omitting the options object entirely
• Confusing update with replace option

3. Given the collection users with documents:
{ _id: 1, name: "Alice", age: 25 }
What will be the result after running:

db.users.updateOne({ _id: 2 }, { $set: { name: "Bob", age: 30 } }, { upsert: true })

and then querying db.users.find().toArray()?

medium

A. [{ _id: 1, name: "Alice", age: 25 }, { _id: 2, name: "Bob", age: 30 }]

B. [{ _id: 1, name: "Alice", age: 25 }]

C. [{ _id: 2, name: "Bob", age: 30 }]

D. []

Solution

1. Step 1: Understand the updateOne with upsert

   The filter looks for _id: 2, which does not exist, so upsert inserts a new document with _id: 2 and the given fields.

2. Step 2: Check existing documents

   The original document with _id: 1 remains unchanged, so the collection now has two documents.

3. Final Answer:

   [{ _id: 1, name: "Alice", age: 25 }, { _id: 2, name: "Bob", age: 30 }] -> Option A

4. Quick Check:

   Upsert inserts missing document, keeps existing [OK]

Hint: Upsert inserts new if filter misses existing docs [OK]

Common Mistakes:

• Assuming existing documents get deleted
• Thinking upsert only updates existing documents
• Expecting only the new document after upsert

4. You run the following code but it does not insert a new document when no match is found:

db.products.updateOne({ sku: "123" }, { price: 19.99 })

What is the likely error?

medium

A. The filter syntax is incorrect and causes a syntax error.

B. MongoDB does not support upsert with updateOne.

C. The update document is missing the $set operator.

D. Missing the upsert: true option in the updateOne call.

Solution

1. Step 1: Check the updateOne parameters

   The updateOne call lacks the options object with upsert: true, so it only updates existing documents.

2. Step 2: Confirm upsert behavior

   Without upsert: true, no new document is inserted if the filter finds no match.

3. Final Answer:

   Missing the upsert: true option in the updateOne call. -> Option D

4. Quick Check:

   Upsert option needed to insert new docs [OK]

Hint: Add {upsert: true} to updateOne options to insert [OK]

Common Mistakes:

• Forgetting to add upsert option
• Confusing missing $set with upsert behavior
• Believing updateOne cannot upsert

5. You want to update the status field to "active" for a user with email: "[e-mail]". If no such user exists, insert a new document with email and status. Which MongoDB command correctly achieves this?

hard

A. db.users.updateOne({ email: "[e-mail]" }, { $set: { status: "active" } }, { upsert: true })

B. db.users.insertOne({ email: "[e-mail]", status: "active" })

C. db.users.updateOne({ email: "[e-mail]" }, { status: "active" }, { upsert: true })

D. db.users.updateMany({ email: "[e-mail]" }, { $set: { status: "active" } })

Solution

1. Step 1: Identify the correct update syntax with upsert

   To update or insert, use updateOne with a filter, an update using $set, and {upsert: true} option.

2. Step 2: Check each option

   db.users.updateOne({ email: "[e-mail]" }, { $set: { status: "active" } }, { upsert: true }) uses $set and upsert correctly. db.users.insertOne({ email: "[e-mail]", status: "active" }) only inserts, no update. db.users.updateOne({ email: "[e-mail]" }, { status: "active" }, { upsert: true }) misses $set operator, which replaces the whole document incorrectly. db.users.updateMany({ email: "[e-mail]" }, { $set: { status: "active" } }) updates many but no upsert.

3. Final Answer:

   db.users.updateOne({ email: "[e-mail]" }, { $set: { status: "active" } }, { upsert: true }) -> Option A

4. Quick Check:

   Use updateOne + $set + upsert: true [OK]

Hint: Use $set with upsert: true in updateOne to update or insert [OK]

Common Mistakes:

• Omitting $set causing document replacement
• Using insertOne which does not update
• Forgetting upsert option for insert fallback