Compound queries (multiple where) in Firebase - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ service_behavior

intermediate

Understanding compound queries with multiple where clauses

Consider a Firestore collection named products with documents having fields category (string) and price (number). You want to query products where category is 'electronics' and price is less than 500.

Which query will correctly return the matching documents?

A db.collection('products').where('category', '==', 'electronics').where('price', '>', 500).get()

B db.collection('products').where('category', '==', 'electronics' && 'price', '<', 500).get()

C db.collection('products').where('category', '==', 'electronics').where('price', '<=', 500).get()

D db.collection('products').where('category', '==', 'electronics').where('price', '<', 500).get()

💡 Hint

Remember that Firestore supports chaining multiple where clauses for compound queries.

Option D correctly chains two where clauses: one for category equality and one for price less than 500. Option D is invalid syntax. Option D uses '<=' which includes 500, not strictly less. Option D queries for price greater than 500, which is incorrect.

❓ Architecture

intermediate

Firestore index requirements for compound queries

You have a Firestore query with two where clauses on fields status and priority. What must you ensure for this query to work without errors?

A No index is needed because Firestore automatically indexes all fields

B A composite index on <code>status</code> and <code>priority</code> fields must exist

C Only single-field indexes on <code>status</code> and <code>priority</code> are required

D An index on <code>status</code> only is sufficient

💡 Hint

Firestore requires composite indexes for queries with multiple where clauses on different fields.

Firestore automatically creates single-field indexes but requires a composite index for compound queries involving multiple fields. Without it, the query will fail with an error prompting index creation.

❓ security

advanced

Security rules impact on compound queries

You have Firestore security rules that allow reading documents only if userId field matches the authenticated user's ID. You run a compound query with where('userId', '==', auth.uid) and where('status', '==', 'active'). What will happen if the rules do not explicitly allow filtering by status?

A The query will succeed but only return documents with <code>status</code> 'active' and matching <code>userId</code>

B The query will return documents ignoring the <code>status</code> filter

C The query will fail because Firestore security rules require all queried fields to be allowed

D The query will succeed because <code>userId</code> matches the authenticated user

💡 Hint

Firestore applies security rules to each document returned by the query after server-side filtering.

Option A is correct. The query succeeds and returns only documents matching both conditions because Firestore executes the query server-side, and all returned documents satisfy the security rule (userId matches). Security rules do not need to explicitly reference all query filter fields; they are checked per returned document.

✅ Best Practice

advanced

Optimizing compound queries for performance

You have a Firestore collection with millions of documents. You want to query documents with category == 'books' and rating >= 4. Which approach is best to optimize query performance?

A Create a composite index on <code>category</code> and <code>rating</code> fields and use a compound query with both filters

B Query all documents with <code>category == 'books'</code> and filter <code>rating >= 4</code> in client code

C Use two separate queries for each filter and merge results in client code

D Create single-field indexes on <code>category</code> and <code>rating</code> and query only by <code>category</code>

💡 Hint

Firestore performs best with proper composite indexes for compound queries.

Option A uses a composite index allowing Firestore to efficiently execute the compound query server-side. Options B and C cause large data transfers and client-side filtering, which is inefficient. Option A does not filter by rating server-side.

🧠 Conceptual

expert

Limitations of compound queries in Firestore

Which of the following statements about Firestore compound queries with multiple where clauses is FALSE?

A All fields used in compound queries must be indexed appropriately

B You can combine multiple <code>where</code> clauses on different fields using logical AND

C Firestore supports OR queries natively with multiple <code>where</code> clauses

D Inequality filters (<, <=, >, >=) can only be applied on a single field in a compound query

💡 Hint

Think about how Firestore handles logical operators in queries.

Firestore compound queries combine multiple where clauses with logical AND. It does not support OR queries natively with multiple where clauses. OR queries require different approaches like in or array-contains-any or multiple queries client-side.