Dot notation for embedded documents in MongoDB

Introduction

Dot notation helps you look inside nested parts of your data easily.

You want to find a specific detail inside a nested object in your database.

You need to update a small part inside a bigger document without changing everything.

You want to sort or filter data based on a value inside an embedded document.

You want to show only a small piece of nested data when you get results.

Syntax

MongoDB

db.collection.find({"outer.inner": value})

Use quotes around the field path if it contains special characters.

Dot notation uses a dot (.) to go deeper inside nested documents.

Examples

Find users who live in the city named New York inside their address.

MongoDB

db.users.find({"address.city": "New York"})

Update the phone number of the customer named Alice inside the orders collection.

MongoDB

db.orders.updateOne({"customer.name": "Alice"}, {$set: {"customer.phone": "123-456"}})

Show only the weight inside the details of each product, hiding the _id.

MongoDB

db.products.find({}, {"details.weight": 1, _id: 0})

Sample Program

This query finds all library documents where the book's author's name is John Doe.

MongoDB

db.library.find({"book.author.name": "John Doe"})

Important Notes

Dot notation only works with embedded documents, not arrays directly.

If you want to query inside arrays, use special operators like $elemMatch.

Summary

Dot notation lets you access nested fields inside documents easily.

Use it to find, update, or project parts of embedded documents.

Remember to use quotes if the field names have special characters.

Practice

1. What does dot notation in MongoDB allow you to do with embedded documents?

easy

A. Access nested fields inside embedded documents

B. Create new collections automatically

C. Encrypt data within documents

D. Delete entire databases

Solution

1. Step 1: Understand dot notation purpose

   Dot notation is used to reach inside nested or embedded documents to access specific fields.

2. Step 2: Compare with other options

   Creating collections, encrypting data, or deleting databases are unrelated to dot notation.

3. Final Answer:

   Access nested fields inside embedded documents -> Option A

4. Quick Check:

   Dot notation = Access nested fields [OK]

Hint: Dot notation accesses nested fields using dots [OK]

Common Mistakes:

• Thinking dot notation creates collections
• Confusing dot notation with encryption
• Assuming dot notation deletes data

2. Which of the following is the correct syntax to query the field address.city in MongoDB?

easy

A. { address.city: 'New York' }

B. { address->city: 'New York' }

C. { 'address.city': 'New York' }

D. { address[city]: 'New York' }

Solution

1. Step 1: Understand dot notation syntax in queries

   Field names with dots must be quoted as a single string in MongoDB queries.

2. Step 2: Evaluate each option

   { 'address.city': 'New York' } uses quotes correctly around 'address.city'. Options A, C, and D use invalid syntax.

3. Final Answer:

   { 'address.city': 'New York' } -> Option C

4. Quick Check:

   Quotes needed for dot field names = { 'address.city': 'New York' } [OK]

Hint: Quote dot notation keys in queries [OK]

Common Mistakes:

• Not quoting dot notation keys
• Using arrows or brackets instead of dots
• Using unquoted keys with dots

3. Given the collection documents:

{ name: 'Alice', contact: { phone: '1234', email: '[e-mail]' } }

What will the query db.collection.find({ 'contact.phone': '1234' }) return?

medium

A. Documents where contact.phone equals '1234'

B. Documents where contact.email equals '1234'

C. Documents where name equals '1234'

D. No documents, syntax error

Solution

1. Step 1: Understand the query filter

   The query filters documents where the embedded field contact.phone equals '1234'.

2. Step 2: Match with document data

   The example document has contact.phone as '1234', so it matches and will be returned.

3. Final Answer:

   Documents where contact.phone equals '1234' -> Option A

4. Quick Check:

   Dot notation filters embedded fields = Documents where contact.phone equals '1234' [OK]

Hint: Dot notation filters nested fields directly [OK]

Common Mistakes:

• Confusing phone with email field
• Thinking dot notation causes syntax error
• Assuming it filters top-level fields only

4. What is wrong with this MongoDB query to update the city in an embedded address document?

db.users.updateOne({ name: 'Bob' }, { $set: { address.city: 'Boston' } })

medium

A. Update operator $set is incorrect

B. Field name with dot must be quoted as a string

C. Collection name should be 'user' not 'users'

D. Query filter is missing

Solution

1. Step 1: Check update syntax for embedded fields

   When using dot notation in update keys, the field name must be quoted as a string.

2. Step 2: Analyze the given query

   The query uses address.city without quotes, which causes a syntax error.

3. Final Answer:

   Field name with dot must be quoted as a string -> Option B

4. Quick Check:

   Quote dot notation keys in updates = Field name with dot must be quoted as a string [OK]

Hint: Quote dot notation keys in update documents [OK]

Common Mistakes:

• Not quoting dot notation keys in $set
• Misusing update operators
• Assuming collection name is wrong

5. You have documents with nested structure:

{ _id: 1, profile: { name: 'Eve', contacts: { email: '[e-mail]', phone: '555' } } }

How do you write a query to find documents where the phone number is '555' using dot notation?

hard

A. { 'profile.contacts': { phone: '555' } }

B. { profile.contacts.phone: '555' }

C. { profile.contacts['phone']: '555' }

D. { 'profile.contacts.phone': '555' }

Solution

1. Step 1: Identify the full path to the nested field

   The phone field is inside contacts, which is inside profile, so the path is profile.contacts.phone.

2. Step 2: Use dot notation with quotes in query

   To query nested fields, use quotes around the full dot notation key: 'profile.contacts.phone'.

3. Final Answer:

   { 'profile.contacts.phone': '555' } -> Option D

4. Quick Check:

   Quote full dot notation path in query = { 'profile.contacts.phone': '555' } [OK]

Hint: Quote full dot notation path in queries [OK]

Common Mistakes:

• Not quoting dot notation keys
• Using object instead of dot notation in query
• Using brackets inside dot notation keys