Bird
Raised Fist0
MongoDBquery~5 mins

$rename operator for field names in MongoDB

Choose your learning style10 modes available
Introduction

The $rename operator helps you change the names of fields in your MongoDB documents easily.

You want to fix a typo in a field name across many documents.
You need to update field names to match a new data format.
You want to make field names more descriptive or consistent.
You are merging data and want to avoid field name conflicts.
You want to remove old field names and replace them with new ones.
Syntax
MongoDB
db.collection.updateMany(
  { <filter> },
  { $rename: { "oldFieldName": "newFieldName" } }
)

The $rename operator is used inside an update command.

You can rename multiple fields by adding more pairs inside the $rename object.

Examples
This renames the field username to user_name in all documents in the users collection.
MongoDB
db.users.updateMany({}, { $rename: { "username": "user_name" } })
This renames price to cost and desc to description only for documents where category is "books".
MongoDB
db.products.updateMany(
  { "category": "books" },
  { $rename: { "price": "cost", "desc": "description" } }
)
Sample Program

This example creates a collection items with two documents. It then renames the field price to cost in all documents. Finally, it shows the updated documents.

MongoDB
use shopDB

// Insert sample documents
db.items.insertMany([
  { _id: 1, name: "Pen", price: 1.5 },
  { _id: 2, name: "Notebook", price: 3.0 }
])

// Rename field 'price' to 'cost'
db.items.updateMany({}, { $rename: { "price": "cost" } })

// Find all documents to see the change
db.items.find().pretty()
OutputSuccess
Important Notes

If the new field name already exists in a document, $rename will overwrite it.

You cannot rename a field to the same name it already has.

Summary

$rename changes field names in MongoDB documents.

It works inside update commands like updateMany.

You can rename one or many fields at once.

Practice

(1/5)
1. What does the $rename operator do in MongoDB?
easy
A. It changes the value of a field in documents.
B. It deletes a field from documents.
C. It changes the name of a field in documents.
D. It adds a new field to documents.

Solution

  1. Step 1: Understand the purpose of $rename

    The $rename operator is used to change the name of an existing field in MongoDB documents.
  2. Step 2: Compare with other update operators

    Unlike $unset which deletes fields, or $set which changes values or adds fields, $rename only changes field names.
  3. Final Answer:

    It changes the name of a field in documents. -> Option C
  4. Quick Check:

    $rename changes field names [OK]
Hint: Remember: $rename changes field names, not values or deletion [OK]
Common Mistakes:
  • Confusing $rename with $set or $unset
  • Thinking $rename changes field values
  • Assuming $rename adds new fields
2. Which of the following is the correct syntax to rename the field oldName to newName in all documents of a collection named users?
easy
A. db.users.updateMany({}, { $rename: { oldName: newName } })
B. db.users.updateMany({}, { $rename: { oldName: 'newName' } })
C. db.users.updateMany({}, { $rename: { 'oldName': newName } })
D. db.users.updateMany({}, { $rename: { 'oldName': 'newName' } })

Solution

  1. Step 1: Check the syntax for $rename

    The $rename operator requires a mapping object where both old and new field names are strings, so keys and values must be quoted.
  2. Step 2: Validate each option

    db.users.updateMany({}, { $rename: { 'oldName': 'newName' } }) correctly uses quotes around both 'oldName' and 'newName'. Options A, C, and D miss quotes on either key or value, causing syntax errors.
  3. Final Answer:

    db.users.updateMany({}, { $rename: { 'oldName': 'newName' } }) -> Option D
  4. Quick Check:

    Field names in $rename must be strings [OK]
Hint: Always quote both old and new field names in $rename [OK]
Common Mistakes:
  • Not quoting field names as strings
  • Using variables instead of strings
  • Mixing quotes and no quotes
3. Given the collection products with documents:
{ "_id": 1, "name": "Pen", "cost": 5 }

What will be the document after running:
db.products.updateOne({ _id: 1 }, { $rename: { "cost": "price" } })

and then fetching the document with db.products.findOne({ _id: 1 })?
medium
A. { "_id": 1, "name": "Pen", "price": 5 }
B. { "_id": 1, "name": "Pen", "cost": 5, "price": 5 }
C. { "_id": 1, "name": "Pen" }
D. { "_id": 1, "name": "Pen", "cost": 5 }

Solution

  1. Step 1: Understand what $rename does in updateOne

    The $rename operator changes the field name from cost to price in the matched document.
  2. Step 2: Predict the document after update

    The field cost is removed and replaced by price with the same value 5. Other fields remain unchanged.
  3. Final Answer:

    { "_id": 1, "name": "Pen", "price": 5 } -> Option A
  4. Quick Check:

    $rename moves field value to new name [OK]
Hint: Rename moves value, old field disappears [OK]
Common Mistakes:
  • Expecting both old and new fields to exist
  • Thinking $rename changes field values
  • Assuming $rename deletes other fields
4. You run the following command:
db.orders.updateMany({}, { $rename: { "orderDate": "date" } })

but get an error. What is the most likely cause?
medium
A. The collection orders does not exist.
B. The new field name "date" already exists in some documents.
C. Field names in $rename must be quoted strings.
D. The updateMany command requires a filter other than {}.

Solution

  1. Step 1: Analyze the error cause for $rename

    If the new field name already exists in documents, MongoDB throws an error because it cannot rename a field to an existing field name.
  2. Step 2: Check other options

    Field names in $rename must be quoted strings. is incorrect because field names are quoted correctly. The collection orders does not exist. is unlikely as the error is specific to $rename. The updateMany command requires a filter other than {}. is invalid because {} is a valid filter for updateMany.
  3. Final Answer:

    The new field name "date" already exists in some documents. -> Option B
  4. Quick Check:

    $rename fails if new field exists [OK]
Hint: Cannot rename to existing field name [OK]
Common Mistakes:
  • Ignoring existing fields with new name
  • Assuming empty filter is invalid
  • Confusing syntax errors with runtime errors
5. You have a collection employees with documents containing fields fname and lname. You want to rename fname to firstName and lname to lastName in one update command. Which command correctly does this?
hard
A. db.employees.updateMany({}, { $rename: { 'fname': 'firstName', 'lname': 'lastName' } })
B. db.employees.updateMany({}, { $rename: { 'fname': 'firstName' }, { 'lname': 'lastName' } })
C. db.employees.updateMany({}, { $rename: { fname: 'firstName', lname: 'lastName' } })
D. db.employees.updateMany({}, { $rename: { 'fname': firstName, 'lname': lastName } })

Solution

  1. Step 1: Understand $rename supports multiple fields

    The $rename operator accepts an object mapping old field names to new field names, allowing multiple renames in one command.
  2. Step 2: Check syntax correctness

    db.employees.updateMany({}, { $rename: { 'fname': 'firstName', 'lname': 'lastName' } }) correctly uses a single object with quoted old and new field names. db.employees.updateMany({}, { $rename: { 'fname': 'firstName' }, { 'lname': 'lastName' } }) has invalid syntax with two separate objects. db.employees.updateMany({}, { $rename: { fname: 'firstName', lname: 'lastName' } }) misses quotes on keys. db.employees.updateMany({}, { $rename: { 'fname': firstName, 'lname': lastName } }) misses quotes on new field names.
  3. Final Answer:

    db.employees.updateMany({}, { $rename: { 'fname': 'firstName', 'lname': 'lastName' } }) -> Option A
  4. Quick Check:

    Multiple renames use one $rename object with string keys and values [OK]
Hint: Use one $rename object with all old:new pairs quoted [OK]
Common Mistakes:
  • Trying multiple $rename objects in one update
  • Not quoting new field names
  • Using variables instead of strings
Recommended

Ready to prove it?

Pass the test and this pattern moves unknown strong while earning +1 Grip toward your certificate.

10 questions~5 mineasy hard