Why logical operators matter in MongoDB - Performance Analysis

Time Complexity: Why logical operators matter

O(n x m)

Understanding Time Complexity

When using logical operators in MongoDB queries, the way they combine conditions affects how long the query takes to run.

We want to understand how the number of conditions and their arrangement change the work the database does.

Scenario Under Consideration

Analyze the time complexity of the following MongoDB query using logical operators.

db.collection.find({
  $or: [
    { age: { $gt: 30 } },
    { status: 'active' },
    { score: { $lt: 50 } }
  ]
})

This query finds documents where age is over 30, or status is active, or score is less than 50.

Identify Repeating Operations

Identify the loops, recursion, array traversals that repeat.

• Primary operation: Checking each document against each condition inside the $or array.
• How many times: Each document is tested against each condition until one matches or all fail.

How Execution Grows With Input

As the number of documents grows, the database checks more items. Also, more conditions inside $or mean more checks per document.

Input Size (n)	Approx. Operations
10 documents	About 10 x 3 = 30 checks
100 documents	About 100 x 3 = 300 checks
1000 documents	About 1000 x 3 = 3000 checks

Pattern observation: The work grows directly with the number of documents and the number of conditions combined by $or.

Final Time Complexity

Time Complexity: O(n * m)

This means the time grows with both the number of documents (n) and the number of conditions (m) inside the logical operator.

Common Mistake

[X] Wrong: "Adding more conditions inside $or doesn't affect query speed much because it stops at the first match."

[OK] Correct: While $or stops checking conditions once one matches per document, the database still must check each document against conditions until one matches or all fail, so more conditions can increase total checks especially if matches are rare.

Interview Connect

Understanding how logical operators affect query time helps you write efficient database queries and explain your reasoning clearly in interviews.

Self-Check

"What if we replaced $or with $and? How would the time complexity change?"

Practice

1. Which logical operator in MongoDB requires all conditions to be true for a document to match?

easy

A. $and

B. $or

C. $not

D. $nor

Solution

1. Step 1: Recall MongoDB logical operators

   $and combines multiple conditions and only matches documents where every condition is true. $or matches if any condition is true, $not excludes matches, and $nor matches if none are true.

2. Final Answer:

   $and -> Option A

3. Quick Check:

   $and requires all true [OK]

Hint: Remember $and means all conditions must be true [OK]

Common Mistakes:

• Confusing $and with $or
• Thinking $not means all true
• Mixing $nor with $and

2. Which of the following is the correct syntax to find documents where age is greater than 25 or status is "active" in MongoDB?

easy

A. { $and: [ { age: { $gt: 25 } }, { status: "active" } ] }

B. { $nor: [ { age: { $gt: 25 } }, { status: "active" } ] }

C. { $not: [ { age: { $gt: 25 } }, { status: "active" } ] }

D. { $or: [ { age: { $gt: 25 } }, { status: "active" } ] }

Solution

1. Step 1: Identify $or operator and verify syntax

   $or matches documents where at least one condition is true, perfect for age > 25 or status = "active". The syntax with $or and array of conditions is correct; $and requires both true, $not and $nor have different meanings.

2. Final Answer:

   { $or: [ { age: { $gt: 25 } }, { status: "active" } ] } -> Option D

3. Quick Check:

   $or for either condition true = { $or: [ { age: { $gt: 25 } }, { status: "active" } ] } [OK]

Hint: Use $or for any condition true, syntax needs array [OK]

Common Mistakes:

• Using $and instead of $or
• Wrong array brackets
• Using $not with array incorrectly

3. Given the collection documents:
{ name: "Alice", age: 30, status: "active" }
{ name: "Bob", age: 20, status: "inactive" }
{ name: "Carol", age: 25, status: "active" }
What will the query { $and: [ { age: { $gt: 20 } }, { status: "active" } ] } return?

medium

A. [{ name: "Bob", age: 20, status: "inactive" }]

B. [{ name: "Alice", age: 30, status: "active" }, { name: "Carol", age: 25, status: "active" }]

C. [{ name: "Alice", age: 30, status: "active" }]

D. []

Solution

1. Step 1: Evaluate documents against $and conditions

   age > 20 and status = "active": Alice (30, active) matches, Carol (25, active) matches, Bob (20, inactive) does not. Both Alice and Carol returned.

2. Final Answer:

   [{ name: "Alice", age: 30, status: "active" }, { name: "Carol", age: 25, status: "active" }] -> Option B

3. Quick Check:

   Both age > 20 and active status = [{ name: "Alice", age: 30, status: "active" }, { name: "Carol", age: 25, status: "active" }] [OK]

Hint: Check each condition carefully for all documents [OK]

Common Mistakes:

• Including Bob who fails conditions
• Returning only one document
• Confusing $and with $or results

4. You wrote this query to exclude documents where status is "inactive":
{ $not: { status: "inactive" } }
But it returns an error. What is the problem?

medium

A. $not must be inside $and

B. $not cannot be used with strings

C. $not requires a condition operator like $eq, not a direct value

D. $not only works with numeric fields

Solution

1. Step 1: Identify $not syntax error

   $not expects a condition operator like { status: { $not: { $eq: "inactive" } } }, not { $not: { status: "inactive" } } with direct value.

2. Final Answer:

   $not requires a condition operator like $eq, not a direct value -> Option C

3. Quick Check:

   $not needs operator condition [OK]

Hint: Use $not with operators like $eq, not direct values [OK]

Common Mistakes:

• Passing direct values to $not
• Assuming $not works alone
• Using $not with arrays incorrectly

5. You want to find documents where age is greater than 20 but NOT with status equal to "inactive". Which query correctly uses logical operators to achieve this?

hard

A. { $and: [ { age: { $gt: 20 } }, { status: { $ne: "inactive" } } ] }

B. { $and: [ { age: { $gt: 20 } }, { $not: { status: { $eq: "inactive" } } } ] }

C. { $or: [ { age: { $gt: 20 } }, { $not: { status: { $eq: "inactive" } } } ] }

D. { $and: [ { age: { $gt: 20 } }, { $not: { status: "inactive" } } ] }

Solution

1. Step 1: Analyze requirement and options

   Need age > 20 AND status != "inactive". A: $not with direct value (invalid). B: $not wrongly placed at top-level; must be { status: { $not: { $eq: "inactive" } } } (but $ne simpler). C: $or allows documents failing one condition. D: Correctly uses $and with $gt and $ne.

2. Final Answer:

   { $and: [ { age: { $gt: 20 } }, { status: { $ne: "inactive" } } ] } -> Option A

3. Quick Check:

   Use $ne for NOT equal, combine with $and = { $and: [ { age: { $gt: 20 } }, { status: { $ne: "inactive" } } ] } [OK]

Hint: Use $ne for NOT equal, combine with $and for all true [OK]

Common Mistakes:

• Using $not with direct value
• Using $or instead of $and
• Overcomplicating with $not and $eq