Querying nested fields at any depth in MongoDB - Step-by-Step Execution

Concept Flow - Querying nested fields at any depth

Start with collection

↓

Specify nested field path

↓

Use dot notation to access nested field

↓

Apply query condition on nested field

↓

MongoDB searches documents

↓

Return matching documents

The query uses dot notation to specify nested fields at any depth and applies conditions to find matching documents.

Execution Sample

MongoDB

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

Finds all users whose nested field 'address.city' equals 'New York'.

Execution Table

Step	Action	Query Part	Documents Checked	Match Found	Result
1	Start query	db.users.find({"address.city": "New York"})	All documents in users	N/A	No output yet
2	Check first document	"address.city" = "New York"?	Doc 1	Yes	Include Doc 1 in results
3	Check second document	"address.city" = "New York"?	Doc 2	No	Exclude Doc 2
4	Check third document	"address.city" = "New York"?	Doc 3	Yes	Include Doc 3 in results
5	Finish scanning	All documents checked	All docs	N/A	Return matched documents (Doc 1, Doc 3)

💡 All documents checked; query returns documents where nested field matches condition.

Variable Tracker

Variable	Start	After Doc 1	After Doc 2	After Doc 3	Final
MatchedDocuments	[]	[Doc 1]	[Doc 1]	[Doc 1, Doc 3]	[Doc 1, Doc 3]

Key Moments - 2 Insights

How does MongoDB know which nested field to check?

MongoDB uses dot notation like "address.city" to look inside nested objects. See execution_table rows 2-4 where it checks that exact path.

What if the nested field does not exist in a document?

If the nested field is missing, the condition is false for that document, so it is excluded. This is shown in execution_table row 3 where Doc 2 does not match.

Visual Quiz - 3 Questions

Look at the execution table, which documents matched the query?

A Doc 2 only

B Doc 1 and Doc 3

C Doc 1 only

D No documents matched

💡 Hint

Check the 'Match Found' and 'Result' columns in rows 2, 3, and 4.

At which step does the query finish scanning all documents?

A Step 3

B Step 2

C Step 5

D Step 4

💡 Hint

Look at the 'Step' and 'Action' columns for when all documents are checked.

If the nested field was "address.zipcode" instead, how would the query change?

A Use {"address.zipcode": value} in the query

B Use {"address.city": value} in the query

C Use {"zipcode": value} in the query

D Use {"address": {"zipcode": value}} in the query

💡 Hint

Dot notation accesses nested fields; see the query in execution_sample.

Concept Snapshot

Query nested fields using dot notation:
- Use "field.subfield" to access nested data
- Apply conditions on nested fields directly
- MongoDB returns documents matching the nested condition
- Works at any depth by chaining dots
- Missing nested fields cause no match

Full Transcript

This visual execution shows how MongoDB queries nested fields at any depth using dot notation. The query specifies the nested field path like "address.city" and applies a condition. MongoDB scans each document in the collection, checks if the nested field matches the condition, and includes matching documents in the result. Documents missing the nested field do not match. The process ends after all documents are checked, returning only those that satisfy the nested field condition.

Practice

1. Which MongoDB query syntax correctly accesses a nested field named address.city inside a document?

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 for nested fields

   MongoDB uses dot notation like "address.city" to access nested fields inside documents.

2. Step 2: Identify correct query syntax

   The correct query uses a string key with dot notation: { "address.city": "New York" }.

3. Final Answer:

   { "address.city": "New York" } -> Option D

4. Quick Check:

   Dot notation = { "address.city": value } [OK]

Hint: Use quotes and dot notation to access nested fields [OK]

Common Mistakes:

• Using nested objects instead of dot notation in query
• Using arrow or parentheses instead of dot notation
• Not quoting the nested field path

2. Which of the following is the correct MongoDB query to find documents where the nested field profile.details.age equals 30?

easy

A. { profile.details.age = 30 }

B. { "profile.details.age": 30 }

C. { profile.details.age: 30 }

D. { 'profile.details.age' == 30 }

Solution

1. Step 1: Use string keys with dot notation in MongoDB queries

   MongoDB requires the nested field path as a string key with dots, like "profile.details.age".

2. Step 2: Use colon for key-value pairs in query objects

   The correct syntax uses colon (:), not equals (=) or double equals (==), so { "profile.details.age": 30 } is correct.

3. Final Answer:

   { "profile.details.age": 30 } -> Option B

4. Quick Check:

   Dot notation with colon = correct query [OK]

Hint: Use colon and quotes for nested keys in queries [OK]

Common Mistakes:

• Using = or == instead of colon in query
• Not quoting the nested field path
• Using object notation instead of dot notation

3. Given the collection documents:

{ "user": { "contact": { "email": "[e-mail]" } } }, { "user": { "contact": { "email": "[e-mail]" } } }, { "user": { "contact": { "phone": "12345" } } }

What will the query db.collection.find({ "user.contact.email": { $exists: true } }) return?

medium

A. Documents where user.contact has any field

B. Documents where user.contact.phone exists

C. Documents where user.contact.email exists

D. All documents in the collection

Solution

1. Step 1: Understand $exists operator with nested fields

   The query checks if the nested field "user.contact.email" exists in documents.

2. Step 2: Identify which documents have that nested field

   Only the first two documents have "user.contact.email"; the third has "user.contact.phone" instead.

3. Final Answer:

   Documents where user.contact.email exists -> Option C

4. Quick Check:

   $exists true filters documents with that nested field [OK]

Hint: Use $exists to check nested field presence [OK]

Common Mistakes:

• Assuming $exists checks parent fields
• Confusing email and phone fields
• Expecting all documents to match

4. You wrote this query to find documents where profile.address.zipcode is "12345":

db.users.find({ profile.address.zipcode: "12345" })

But it gives a syntax error. What is the fix?

medium

A. Use quotes around the nested field: { "profile.address.zipcode": "12345" }

B. Replace dots with underscores: { profile_address_zipcode: "12345" }

C. Use double equals: { "profile.address.zipcode" == "12345" }

D. Remove the nested field and query only { zipcode: "12345" }

Solution

1. Step 1: Identify syntax error cause

   MongoDB requires string keys with dot notation quoted in queries to avoid syntax errors.

2. Step 2: Correct query syntax

   Wrap the nested field path in quotes: { "profile.address.zipcode": "12345" } fixes the syntax error.

3. Final Answer:

   Use quotes around the nested field: { "profile.address.zipcode": "12345" } -> Option A

4. Quick Check:

   Quotes fix dot notation syntax errors [OK]

Hint: Always quote nested field keys in queries [OK]

Common Mistakes:

• Not quoting nested field keys
• Using == instead of colon
• Replacing dots with underscores incorrectly

5. You have documents with deeply nested fields like settings.preferences.notifications.email.enabled. How would you write a MongoDB query to find all documents where email notifications are enabled (true), regardless of nesting depth?

hard

A. { "settings.preferences.notifications.email.enabled": true }

B. { settings: { preferences: { notifications: { email: { enabled: true } } } } }

C. { "email.enabled": true }

D. { "settings.preferences.notifications.email.enabled": { $eq: "true" } }

Solution

1. Step 1: Use dot notation string to access deeply nested field

   MongoDB queries use dot notation strings to reach any depth, so "settings.preferences.notifications.email.enabled" is correct.

2. Step 2: Match boolean value correctly

   Use true (boolean) without quotes to match enabled field, so { "settings.preferences.notifications.email.enabled": true } is correct.

3. Final Answer:

   { "settings.preferences.notifications.email.enabled": true } -> Option A

4. Quick Check:

   Dot notation + boolean value = correct query [OK]

Hint: Use full dot path with boolean true (no quotes) [OK]

Common Mistakes:

• Using nested objects instead of dot notation
• Quoting boolean true as string
• Using partial nested paths