Compound queries (multiple where) in Firebase - Time & Space Complexity

Time Complexity: Compound queries (multiple where)

O(n * k)

Understanding Time Complexity

When using compound queries with multiple conditions in Firebase, it's important to understand how the number of conditions affects the work done behind the scenes.

We want to know how the time to get results changes as we add more conditions.

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);

const results = await query.get();
    

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

Identify Repeating Operations

Identify the API calls, resource provisioning, data transfers that repeat.

• Primary operation: Executing the query with multiple where conditions.
• How many times: Each condition adds one filter operation internally.

How Execution Grows With Input

Each added condition narrows down the data, but the query engine must check each condition for every relevant document.

Input Size (n)	Approx. Api Calls/Operations
10	About 3 filter checks per document, total ~30 checks
100	About 3 filter checks per document, total ~300 checks
1000	About 3 filter checks per document, total ~3000 checks

Pattern observation: The total checks grow roughly in proportion to the number of documents times the number of conditions.

Final Time Complexity

Time Complexity: O(n * k)

This means the time grows with the number of documents (n) and the number of conditions (k) in the query.

Common Mistake

[X] Wrong: "Adding more where conditions does not affect query time because the database is optimized."

[OK] Correct: Each condition adds work to check documents, so more conditions mean more checks, increasing time.

Interview Connect

Understanding how query complexity grows helps you design efficient data fetching and shows you can think about performance in real projects.

Self-Check

"What if we replaced multiple where conditions with a single composite index? How would the time complexity change?"

Practice

1. What does a compound query with multiple .where() filters do in Firebase Firestore?

easy

A. It deletes documents that match the conditions.

B. It finds documents that match any one of the specified conditions.

C. It finds documents that match all the specified conditions.

D. It updates documents that match the conditions.

Solution

1. Step 1: Understand the purpose of .where() filters

   Each .where() filter narrows down the documents by a condition.

2. Step 2: Combine multiple filters in a compound query

   Multiple .where() filters together find documents matching all conditions (AND logic).

3. Final Answer:

   It finds documents that match all the specified conditions. -> Option C

4. Quick Check:

   Compound query = all conditions matched [OK]

Hint: Multiple .where() means all conditions must be true [OK]

Common Mistakes:

• Thinking it matches any condition (OR logic)
• Confusing query with update or delete
• Assuming it returns all documents

2. Which of the following is the correct syntax to create a compound query with two .where() filters in Firebase Firestore?

easy

A. db.collection('users').where(['age', '>=', 18], ['status', '==', 'active'])

B. db.collection('users').where('age', '>=', 18, 'status', '==', 'active')

C. db.collection('users').filter('age', '>=', 18).filter('status', '==', 'active')

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

Solution

1. Step 1: Review Firestore query chaining syntax

   Each .where() is chained separately with three arguments: field, operator, value.

2. Step 2: Identify correct chaining of two .where() calls

   db.collection('users').where('status', '==', 'active').where('age', '>=', 18) correctly chains two .where() calls with proper arguments.

3. Final Answer:

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

4. Quick Check:

   Separate .where() calls chained = correct syntax [OK]

Hint: Chain separate .where() calls with 3 arguments each [OK]

Common Mistakes:

• Passing multiple conditions in one .where() call
• Using .filter() instead of .where()
• Incorrect argument grouping inside .where()

3. Given the following Firestore query:

db.collection('orders')
  .where('status', '==', 'shipped')
  .where('total', '>', 100)

What documents will this query return?

medium

A. Orders with status 'shipped' only.

B. Orders with status 'shipped' and total greater than 100.

C. Orders with total greater than 100 only.

D. Orders with status 'shipped' or total greater than 100.

Solution

1. Step 1: Analyze the two .where() filters

   First filter: status must be 'shipped'. Second filter: total must be greater than 100.

2. Step 2: Understand compound query logic

   Both conditions must be true for a document to be returned.

3. Final Answer:

   Orders with status 'shipped' and total greater than 100. -> Option B

4. Quick Check:

   Multiple .where() = AND logic [OK]

Hint: Multiple .where() means all conditions must match [OK]

Common Mistakes:

• Thinking it uses OR logic
• Ignoring one of the filters
• Confusing field names or operators

4. You wrote this Firestore query:

db.collection('products')
  .where('category', '==', 'books')
  .where('price', '<', 20)
  .where('price', '>', 5)
  .orderBy('price')

But Firestore returns an error about missing index. What is the best way to fix this?

medium

A. Create a composite index for 'category' and 'price' fields as requested by Firestore.

B. Remove one of the .where() filters to avoid multiple conditions.

C. Change the query to use only one .where() filter.

D. Rewrite the query using .orderBy() instead of .where().

Solution

1. Step 1: Understand Firestore index requirements for compound queries

   Firestore requires composite indexes for queries with multiple .where() filters on different fields or range filters.

2. Step 2: Follow Firestore error message instructions

   Firestore error usually provides a link to create the needed composite index.

3. Final Answer:

   Create a composite index for 'category' and 'price' fields as requested by Firestore. -> Option A

4. Quick Check:

   Missing index error = create composite index [OK]

Hint: Create composite index when Firestore asks [OK]

Common Mistakes:

• Removing filters instead of creating index
• Ignoring Firestore error message
• Trying to replace .where() with .orderBy() incorrectly

5. You want to query a Firestore collection 'events' for documents where type is 'conference', attendees is greater than 100, and location is 'NYC'. Which of the following is the best approach to write this compound query and ensure it works efficiently?

hard

A. Chain three .where() filters for each condition and create a composite index for these fields.

B. Use a single .where() with an array of conditions for all fields.

C. Query only by type and filter the rest in client code.

D. Use .orderBy() on all fields instead of .where().

Solution

1. Step 1: Write the compound query with multiple .where() filters

   Use .where('type', '==', 'conference'), .where('location', '==', 'NYC'), and .where('attendees', '>', 100) chained together.

2. Step 2: Ensure Firestore has a composite index for these fields

   Because multiple filters on different fields are used, create a composite index to optimize query performance and avoid errors.

3. Final Answer:

   Chain three .where() filters and create a composite index for these fields. -> Option A

4. Quick Check:

   Multiple filters + composite index = efficient query [OK]

Hint: Chain .where() and create composite index for multiple fields [OK]

Common Mistakes:

• Trying to put all conditions in one .where() call
• Filtering on client side instead of query
• Using .orderBy() instead of .where() for filtering