Query limitations and workarounds in Firebase - Time & Space Complexity

Time Complexity: Query limitations and workarounds

O(n)

Understanding Time Complexity

When using Firebase queries, some limits affect how many operations run as data grows.

We want to see how query limits impact the number of calls as data size increases.

Scenario Under Consideration

Analyze the time complexity of paginated queries with limits.

const pageSize = 10;
let lastVisible = null;

async function getNextPage() {
  let query = firestore.collection('items').orderBy('timestamp').limit(pageSize);
  if (lastVisible) {
    query = query.startAfter(lastVisible);
  }
  const snapshot = await query.get();
  lastVisible = snapshot.docs[snapshot.docs.length - 1];
  return snapshot.docs.map(doc => doc.data());
}
    

This code fetches data in pages of 10 items, using the last item as a cursor for the next page.

Identify Repeating Operations

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

• Primary operation: Querying a page of data with a limit and cursor.
• How many times: Once per page requested by the user.

How Execution Grows With Input

Each page fetch makes one query call returning a fixed number of items.

Input Size (n)	Approx. Api Calls/Operations
10	1 query call
100	10 query calls (10 pages)
1000	100 query calls (100 pages)

Pattern observation: The number of query calls grows linearly with the number of pages requested.

Final Time Complexity

Time Complexity: O(n)

This means the total number of queries grows directly with how many items you want to fetch.

Common Mistake

[X] Wrong: "Fetching more data pages will still be just one query call."

[OK] Correct: Each page requires a separate query call, so more pages mean more calls.

Interview Connect

Understanding how query limits affect calls helps you design efficient data fetching in real apps.

Self-Check

"What if we removed the limit and tried to fetch all data at once? How would the time complexity change?"

Practice

1. What is a common limitation when using Firebase queries with multiple filters?

easy

A. You can only apply range filters on a single field at a time.

B. You can apply unlimited filters on any fields without restrictions.

C. Firebase automatically merges all filters without any index setup.

D. You cannot use any filters with Firebase queries.

Solution

1. Step 1: Understand Firebase query filter limits

   Firebase allows only one range filter (like greater than or less than) on a single field per query to maintain performance.

2. Step 2: Recognize the impact on multiple filters

   Applying multiple range filters on different fields is not allowed, so you must design queries accordingly.

3. Final Answer:

   You can only apply range filters on a single field at a time. -> Option A

4. Quick Check:

   Range filters limited to one field = B [OK]

Hint: Only one range filter per query field allowed [OK]

Common Mistakes:

• Thinking multiple range filters on different fields are allowed
• Assuming no index setup is needed for filters
• Believing unlimited filters can be combined

2. Which of the following is the correct syntax to add a filter for documents where the field age is greater than 18 in Firebase Firestore?

easy

A. db.collection('users').filter('age' > 18)

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

C. db.collection('users').where('age' => 18)

D. db.collection('users').query('age', '>', 18)

Solution

1. Step 1: Recall Firestore query syntax

   The correct method to filter documents is using where(field, operator, value).

2. Step 2: Match the correct operator and syntax

   The operator for greater than is '>', so where('age', '>', 18) is correct.

3. Final Answer:

   db.collection('users').where('age', '>', 18) -> Option B

4. Quick Check:

   Use where with operator '>' = A [OK]

Hint: Use where(field, operator, value) for filters [OK]

Common Mistakes:

• Using incorrect method names like filter or query
• Using wrong operator symbols like =>
• Missing quotes around operator

3. Consider this Firestore query code:

db.collection('products')
  .where('price', '>=', 10)
  .where('price', '<=', 50)
  .where('category', '==', 'books')
  .orderBy('price')
  .get()

What will happen when this query runs?

medium

A. It will return all books priced between 10 and 50 sorted by price.

B. It will throw an error because multiple range filters on the same field are not allowed.

C. It will throw an error because range filters and equality filters cannot be combined.

D. It will return all products without filtering.

Solution

1. Step 1: Analyze the filters used

   The query uses two range filters on the same field 'price' (greater or equal 10 and less or equal 50) and an equality filter on 'category'.

2. Step 2: Check Firebase query rules

   Firebase allows multiple range filters on the same field combined with equality filters on other fields, and ordering by the range field is valid.

3. Final Answer:

   It will return all books priced between 10 and 50 sorted by price. -> Option A

4. Quick Check:

   Multiple range filters on same field allowed = C [OK]

Hint: Multiple range filters on same field are allowed [OK]

Common Mistakes:

• Thinking multiple range filters on same field cause errors
• Assuming equality filters can't combine with range filters
• Ignoring orderBy requirement on range field

4. You wrote this Firestore query:

db.collection('orders')
  .where('status', '==', 'shipped')
  .where('total', '>', 100)
  .where('date', '>', '2023-01-01')
  .get()

But it throws an error. What is the likely cause?

medium

A. Firestore does not support filtering by date.

B. The equality filter must come after range filters.

C. The collection name is incorrect.

D. You cannot have two range filters on different fields in one query.

Solution

1. Step 1: Identify filters used

   The query has one equality filter on 'status' and two range filters on 'total' and 'date' fields.

2. Step 2: Recall Firestore query limitations

   Firestore allows only one range filter on a single field per query, so having range filters on two different fields causes an error.

3. Final Answer:

   You cannot have two range filters on different fields in one query. -> Option D

4. Quick Check:

   Only one range filter field allowed = D [OK]

Hint: Only one range filter field per query allowed [OK]

Common Mistakes:

• Thinking order of filters matters
• Assuming Firestore can't filter by date
• Believing collection name causes this error

5. You need to query a Firestore collection for documents where status is 'active', priority is greater than 5, and createdAt is after '2023-01-01'. How can you work around Firestore's query limitations to get this data?

hard

A. Create a composite field combining priority and createdAt and filter on it.

B. Use a single query with all three filters combined directly.

C. Run two separate queries: one filtering by status and priority, another by status and createdAt, then merge results in code.

D. Use Firestore's built-in full-text search to handle all filters.

Solution

1. Step 1: Understand Firestore query limits

   Firestore does not allow multiple range filters on different fields in a single query.

2. Step 2: Apply workaround using multiple queries

   Run two queries: one filtering by status and priority, another by status and createdAt, then combine results in your application code.

3. Final Answer:

   Run two separate queries: one filtering by status and priority, another by status and createdAt, then merge results in code. -> Option C

4. Quick Check:

   Multiple queries merge workaround = A [OK]

Hint: Split complex filters into multiple queries and merge results [OK]

Common Mistakes:

• Trying to combine all filters in one query causing errors
• Assuming composite fields solve all filter issues
• Expecting Firestore to support full-text search natively