Why compound queries narrow results in Firebase - Performance Analysis

Time Complexity: Why compound queries narrow results

O(1)

Understanding Time Complexity

When using compound queries in Firebase, we want to know how the number of operations changes as we add more filters.

We ask: How does adding conditions affect the work Firebase does to find data?

Scenario Under Consideration

Analyze the time complexity of the following operation sequence.

const query = firestore.collection('users')
  .where('age', '>=', 18)
  .where('city', '==', 'New York')
  .where('active', '==', true)
  .limit(50);
const results = await query.get();
    

This sequence fetches up to 50 users who are adults, live in New York, and are active.

Identify Repeating Operations

• Primary operation: The query request to Firestore server with multiple filters.
• How many times: One query call, but internally Firestore applies each filter to narrow results.

How Execution Grows With Input

Each added filter narrows down the data Firestore must check, so the work does not grow much with more filters.

Input Size (n)	Approx. API Calls/Operations
10	1 query with 3 filters
100	1 query with 3 filters
1000	1 query with 3 filters

Pattern observation: The number of API calls stays the same; filters reduce data scanned internally.

Final Time Complexity

Time Complexity: O(1)

This means adding more filters does not increase the number of query calls; the query narrows results efficiently.

Common Mistake

[X] Wrong: "Adding more filters makes Firebase do more queries and slows things down a lot."

[OK] Correct: Firebase runs one query applying all filters together, so it does not multiply the work by filters.

Interview Connect

Understanding how compound queries work helps you design efficient data fetching in real projects, showing you know how to keep apps fast and responsive.

Self-Check

"What if we removed the limit(50) call? How would the time complexity change?"

Practice

1. What is the main reason compound queries in Firebase narrow down results?

easy

A. They increase the number of documents returned.

B. They combine multiple conditions to filter data more precisely.

C. They ignore some conditions to speed up queries.

D. They randomly select documents from the database.

Solution

1. Step 1: Understand what compound queries do

   Compound queries use more than one condition to filter data.

2. Step 2: Effect of combining conditions

   Combining conditions means only documents matching all conditions are returned, narrowing results.

3. Final Answer:

   They combine multiple conditions to filter data more precisely. -> Option B

4. Quick Check:

   Compound queries = multiple conditions = narrower results [OK]

Hint: Think: More conditions mean fewer matching results [OK]

Common Mistakes:

• Thinking compound queries increase results
• Believing conditions are ignored
• Assuming random selection happens

2. Which of the following is the correct syntax to create a compound query in Firebase Firestore?

easy

A. db.collection('users').query('age', '>=', 18).query('active', '==', true)

B. db.collection('users').filter('age', '>=', 18).filter('active', '==', true)

C. db.collection('users').select('age', 'active')

D. db.collection('users').where('age', '>=', 18).where('active', '==', true)

Solution

1. Step 1: Recall Firestore query syntax

   Firestore uses chained where methods to add conditions.

2. Step 2: Identify correct chaining

   db.collection('users').where('age', '>=', 18).where('active', '==', true) correctly chains two where calls for compound conditions.

3. Final Answer:

   db.collection('users').where('age', '>=', 18).where('active', '==', true) -> Option D

4. Quick Check:

   Compound query syntax uses chained where() calls [OK]

Hint: Remember: Firestore uses chained where() for multiple conditions [OK]

Common Mistakes:

• Using filter() instead of where()
• Using query() which is invalid
• Using select() which only picks fields

3. Given this Firestore query:
db.collection('products').where('price', '<=', 100).where('inStock', '==', true)
What kind of results will this query return?

medium

A. Products priced at 100 or less and currently in stock

B. All products priced above 100 and in stock

C. Products priced at 100 or less regardless of stock

D. Only products that are out of stock

Solution

1. Step 1: Analyze the first condition

   The query filters products with price less than or equal to 100.

2. Step 2: Analyze the second condition

   It also filters products where inStock is true, meaning available products.

3. Final Answer:

   Products priced at 100 or less and currently in stock -> Option A

4. Quick Check:

   Compound query narrows to price ≤ 100 AND inStock = true [OK]

Hint: Both conditions must be true for results [OK]

Common Mistakes:

• Ignoring the inStock condition
• Thinking price > 100 is included
• Confusing AND with OR logic

4. You wrote this query:
db.collection('orders').where('status', '==', 'shipped').where('status', '==', 'delivered')
Why does this query return no results?

medium

A. Because the collection 'orders' does not exist.

B. Because the syntax for multiple where clauses is incorrect.

C. Because a document cannot have 'status' equal to both 'shipped' and 'delivered' at the same time.

D. Because Firestore does not support queries on the 'status' field.

Solution

1. Step 1: Understand the conditions on the same field

   The query asks for documents where 'status' equals 'shipped' AND 'delivered' simultaneously.

2. Step 2: Realize the logical impossibility

   A single field cannot have two different values at once, so no documents match both.

3. Final Answer:

   Because a document cannot have 'status' equal to both 'shipped' and 'delivered' at the same time. -> Option C

4. Quick Check:

   Same field with conflicting conditions returns no results [OK]

Hint: Same field can't equal two different values simultaneously [OK]

Common Mistakes:

• Thinking syntax is wrong
• Assuming Firestore disallows querying 'status'
• Assuming collection absence causes this

5. You want to find users who are both 'active' and have a 'score' greater than 50. Which compound query correctly narrows results to this criteria?

hard

A. db.collection('users').where('active', '==', true).where('score', '>', 50)

B. db.collection('users').where('active', '==', true).where('score', '<', 50)

C. db.collection('users').where('active', '==', false).where('score', '>', 50)

D. db.collection('users').where('active', '==', true).where('score', '==', 50)

Solution

1. Step 1: Identify the conditions needed

   Users must be 'active' (true) and have 'score' greater than 50.

2. Step 2: Match conditions to query options

   db.collection('users').where('active', '==', true).where('score', '>', 50) matches both conditions correctly: active equals true and score greater than 50.

3. Final Answer:

   db.collection('users').where('active', '==', true).where('score', '>', 50) -> Option A

4. Quick Check:

   Correct compound query matches all criteria [OK]

Hint: Match conditions exactly to narrow results [OK]

Common Mistakes:

• Using wrong comparison operators
• Mixing true/false for active
• Using equality instead of greater than