Query limitations and workarounds in Firebase - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

Understanding Firestore Query Limitations

Firestore queries have some limitations. Which of the following is NOT a Firestore query limitation?

A You cannot perform a query with multiple inequality filters on different fields.

B You cannot perform a query that combines 'OR' conditions directly.

C You cannot query documents without an index on the queried fields.

D You cannot order query results by a field that is not included in the filters.

💡 Hint

Think about what Firestore allows in ordering and filtering.

Firestore allows ordering by fields even if they are not filtered, but it requires indexes for certain queries. Multiple inequality filters on different fields and direct 'OR' queries are not supported.

❓ Architecture

intermediate

Workaround for Firestore 'OR' Queries

You want to query documents where status is 'active' OR priority is 'high'. Firestore does not support 'OR' queries directly. Which approach correctly implements this?

A Perform two separate queries and merge results in the client.

B Use a single query with multiple inequality filters on both fields.

C Create a composite field combining status and priority and query on it.

D Use Firestore's 'array-contains-any' operator on both fields.

💡 Hint

Consider how Firestore handles multiple queries and client-side merging.

Firestore does not support 'OR' queries directly. The common workaround is to run multiple queries and merge results on the client side.

❓ Configuration

advanced

Index Configuration for Complex Queries

You have a Firestore query filtering by category and ordering by timestamp. The query fails due to missing index. Which index configuration is required?

Firebase

collection: products
fields:
  - fieldPath: category
    order: ASCENDING
  - fieldPath: timestamp
    order: DESCENDING

A An index on category ascending and timestamp descending.

B An index on timestamp ascending only.

C An index on category descending and timestamp ascending.

D No index needed; Firestore supports this query by default.

💡 Hint

Check the order directions in the query and index.

Firestore requires a composite index matching the filter and order directions exactly.

❓ service_behavior

advanced

Behavior of Firestore Queries with Inequality Filters

What happens if you try to run a Firestore query with inequality filters on two different fields, for example age > 20 and score < 50?

A The query runs successfully and returns matching documents.

B The query fails with an error about multiple inequality filters.

C The query ignores one of the inequality filters and runs.

D The query runs but returns no documents.

💡 Hint

Recall Firestore's rules on inequality filters.

Firestore does not allow inequality filters on more than one field in a single query.

❓ security

expert

Securing Queries with Firestore Rules and Query Limitations

You want to secure a Firestore collection so users can only read documents where ownerId equals their user ID. You write a security rule using request.auth.uid == resource.data.ownerId. Which query limitation must you consider to ensure the query passes the security rules?

A The query can omit filtering on <code>ownerId</code> because rules handle security.

B The query must order by <code>ownerId</code> but not filter on it.

C The query must include a filter on <code>ownerId</code> equal to the user's ID.

D The query must use a composite index on <code>ownerId</code> and <code>timestamp</code>.

💡 Hint

Think about how Firestore security rules interact with queries.

Firestore requires queries to include filters matching security rules to avoid returning unauthorized data.

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