$and operator behavior in MongoDB - Time & Space Complexity
Start learning this pattern below
Jump into concepts and practice - no test required
When using the $and operator in MongoDB queries, it is important to understand how the query time grows as we add more conditions.
We want to know how the number of conditions affects the work MongoDB does to find matching documents.
Analyze the time complexity of the following MongoDB query using $and.
db.collection.find({
$and: [
{ age: { $gt: 25 } },
{ status: "active" },
{ score: { $gte: 70 } }
]
})
This query finds documents where age is greater than 25, status is "active", and score is at least 70.
Look at what MongoDB does internally to process this query.
- Primary operation: MongoDB checks each condition in the
$andarray for every document it considers. - How many times: For each document, it evaluates all conditions one by one until one fails or all pass.
As the number of conditions in $and grows, MongoDB must check more conditions per document.
| Number of Conditions (n) | Approx. Checks per Document |
|---|---|
| 3 | 3 checks |
| 10 | 10 checks |
| 100 | 100 checks |
Pattern observation: The work grows linearly with the number of conditions because each condition is checked in order.
Time Complexity: O(n)
This means the time to evaluate the $and conditions grows directly in proportion to how many conditions there are.
[X] Wrong: "Adding more conditions inside $and does not affect query time much because MongoDB is fast."
[OK] Correct: Each condition adds extra checks for every document, so more conditions mean more work and longer query time.
Understanding how $and affects query time helps you write efficient queries and explain your reasoning clearly in interviews.
"What if we replaced $and with $or? How would the time complexity change?"
Practice
What does the $and operator do in a MongoDB query?
Solution
Step 1: Understand the purpose of
The$and$andoperator combines multiple conditions and requires all to be true for a document to match.Step 2: Compare with other operators
Unlike$or, which matches if any condition is true,$andneeds all conditions true.Final Answer:
It finds documents that match all the given conditions. -> Option AQuick Check:
$andmeans all conditions must match [OK]
- Confusing $and with $or operator
- Thinking $and sorts documents
- Assuming $and deletes documents
Which of the following is the correct syntax to use $and in a MongoDB query?
{ $and: [ { age: { $gt: 20 } }, { city: "NY" } ] }Solution
Step 1: Recall the syntax of
The$and$andoperator requires an array of condition objects inside square brackets.Step 2: Check each option's structure
{ $and: [ { age: { $gt: 20 } }, { city: "NY" } ] } correctly uses an array with two condition objects. Options A and B use objects instead of arrays, and C uses parentheses which is invalid.Final Answer:
{ $and: [ { age: { $gt: 20 } }, { city: "NY" } ] } -> Option AQuick Check:
$andneeds an array of conditions [OK]
- Using curly braces {} instead of array []
- Using parentheses () instead of array []
- Putting conditions directly without array
Given the collection users with documents:
[{ name: "Alice", age: 25, city: "NY" }, { name: "Bob", age: 30, city: "LA" }, { name: "Carol", age: 25, city: "LA" }]What will the query { $and: [ { age: 25 }, { city: "LA" } ] } return?
Solution
Step 1: Understand the query conditions
The query looks for documents whereageis 25 ANDcityis "LA".Step 2: Check each document against conditions
Alice has age 25 but city "NY" (fails city condition). Bob has city "LA" but age 30 (fails age condition). Carol has age 25 and city "LA" (matches both).Final Answer:
[{ name: "Carol", age: 25, city: "LA" }] -> Option CQuick Check:
Both conditions true only for Carol [OK]
- Selecting documents matching only one condition
- Ignoring the AND logic of $and
- Confusing city names or ages
Consider this query:
{ $and: { age: { $gt: 20 }, city: "NY" } }What is wrong with this query?
Solution
Step 1: Check the structure of $and
The$andoperator requires an array of conditions, but here it is given an object.Step 2: Identify the error
Using an object instead of an array causes a syntax error in MongoDB queries.Final Answer:
The conditions inside $and must be in an array, not an object. -> Option BQuick Check:
$andneeds an array of conditions [OK]
- Using object {} instead of array [] for $and
- Assuming $gt is invalid inside $and
- Thinking string values are not allowed
You want to find documents in a products collection where the price is greater than 100 and the category is either "electronics" or "appliances". Which query correctly uses $and and $or to achieve this?
Solution
Step 1: Understand the conditions
The query needs price > 100 AND category is either "electronics" OR "appliances".Step 2: Check each option's logic
{ $and: [ { price: { $gt: 100 } }, { $or: [ { category: "electronics" }, { category: "appliances" } ] } ] } correctly uses$andwith price condition and an inner$orfor categories. { $or: [ { price: { $gt: 100 } }, { category: "electronics" }, { category: "appliances" } ] } uses$orfor all, which is incorrect. { price: { $gt: 100 }, category: { $or: [ "electronics", "appliances" ] } } uses invalid syntax for$orinside category. { $and: { price: { $gt: 100 }, category: { $in: [ "electronics", "appliances" ] } } } uses$andwith an object instead of array, which is invalid.Final Answer:
{ $and: [ { price: { $gt: 100 } }, { $or: [ { category: "electronics" }, { category: "appliances" } ] } ] } -> Option DQuick Check:
Combine $and for price and $or for categories [OK]
- Using $or for all conditions instead of $and
- Incorrect syntax for $or inside category
- Using object instead of array for $and
