Why updating documents matters in MongoDB - See It in Action

Why Updating Documents Matters in MongoDB

📖 Scenario: You are managing a small online bookstore database using MongoDB. You have a collection of books, and sometimes you need to update the information about a book, like its price or stock quantity, to keep the data accurate and useful for customers.

🎯 Goal: Learn how to update documents in a MongoDB collection to keep your data current and correct.

📋 What You'll Learn

Create a collection called books with three book documents

Add a variable to specify the book to update

Write an update query to change the price of the specified book

Add a final query to confirm the update was successful

💡 Why This Matters

🌍 Real World

Updating documents keeps your database accurate, which is important for online stores, inventory systems, and any app that changes data over time.

💼 Career

Database administrators and backend developers often update documents to reflect real-world changes, such as price changes, stock updates, or user information edits.

1

Create the books collection with initial documents

Create a books collection with these exact three documents: { title: "The Great Gatsby", author: "F. Scott Fitzgerald", price: 10, stock: 5 }, { title: "1984", author: "George Orwell", price: 15, stock: 8 }, and { title: "To Kill a Mockingbird", author: "Harper Lee", price: 12, stock: 7 }.

MongoDB

// Insert the three book documents into the books collection
// Your code here

Hint

Use db.books.insertMany() with an array of objects to add multiple documents at once.

2

Specify the book to update

Create a variable called bookToUpdate and set it to { title: "1984" } to select the book you want to update.

MongoDB

db.books.insertMany([
  { title: "The Great Gatsby", author: "F. Scott Fitzgerald", price: 10, stock: 5 },
  { title: "1984", author: "George Orwell", price: 15, stock: 8 },
  { title: "To Kill a Mockingbird", author: "Harper Lee", price: 12, stock: 7 }
])

// Create a variable bookToUpdate to select the book with title "1984"
// Your code here

Hint

Use const bookToUpdate = { title: "1984" } to create the variable.

3

Update the price of the selected book

Write an update query using db.books.updateOne() to change the price of the book selected by bookToUpdate to 18.

MongoDB

db.books.insertMany([
  { title: "The Great Gatsby", author: "F. Scott Fitzgerald", price: 10, stock: 5 },
  { title: "1984", author: "George Orwell", price: 15, stock: 8 },
  { title: "To Kill a Mockingbird", author: "Harper Lee", price: 12, stock: 7 }
])

const bookToUpdate = { title: "1984" }

// Update the price of the book "1984" to 18
// Your code here

Hint

Use db.books.updateOne(bookToUpdate, { $set: { price: 18 } }) to update the price.

4

Confirm the update by finding the updated document

Write a query using db.books.findOne() with bookToUpdate to retrieve the updated book document.

MongoDB

db.books.insertMany([
  { title: "The Great Gatsby", author: "F. Scott Fitzgerald", price: 10, stock: 5 },
  { title: "1984", author: "George Orwell", price: 15, stock: 8 },
  { title: "To Kill a Mockingbird", author: "Harper Lee", price: 12, stock: 7 }
])

const bookToUpdate = { title: "1984" }

db.books.updateOne(bookToUpdate, { $set: { price: 18 } })

// Find the updated book document
// Your code here

Hint

Use const updatedBook = db.books.findOne(bookToUpdate) to get the updated document.

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