Why should you care?

When a user changes city or an order moves to shipped, you patch one document safely without rewriting unrelated fields.

See it live — copy this example

Open mongosh or MongoDB Compass, select database nosqlverse, then run the example. Change one field and run again.

db.users.insertOne({ username: "neha", city: "Jaipur", loginCount: 2 })
db.users.updateOne(
  { username: "neha" },
  { $set: { city: "Bengaluru" }, $inc: { loginCount: 1 } }
)
db.users.findOne({ username: "neha" })

Run Example »

Edit the code below and click Run to see the result in Toolliyo’s live editor.

What happened?

• The filter finds neha.
• $set updates city.
• $inc adds 1 to loginCount.
• Other fields stay untouched.

Practice next

1. Insert the user and run updateOne.
2. Confirm city and loginCount.
3. Run updateOne with a filter that matches nothing — check matchedCount 0.
4. Add $set: { lastLoginAt: new Date() }.
5. Use upsert: true to insert if missing.

Remember

updateOne patches the first match. Use $set / $inc / $unset. Check matchedCount and modifiedCount.

Zomato rider status flip

When a rider accepts an order, updateOne sets status to "accepted" and increments acceptanceCount.

Outcome: Only that rider document changes — live map updates instantly.