Compound queries (multiple where) in Firebase - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to add a single condition to the Firestore query.

Firebase

const query = firestore.collection('users').where('age', '==', [1]);

Drag options to blanks, or click blank then click option'

Aage

B18

C'18'

D==

Attempts:

3 left

💡 Hint

Common Mistakes

Using quotes around numbers

Using the field name instead of a value

The value for the 'where' condition should be a number without quotes for age.

2fill in blank

medium

Complete the code to add a second condition to the Firestore query.

Firebase

const query = firestore.collection('users').where('age', '>=', 18).where('status', [1], 'active');

Drag options to blanks, or click blank then click option'

A!=

B>=

C<=

D==

Attempts:

3 left

💡 Hint

Common Mistakes

Using '>=' or '<=' instead of '==' for equality

The operator '==' is used to check if the status equals 'active'.

3fill in blank

hard

Fix the error in the Firestore query that tries to use an unsupported operator.

Firebase

const query = firestore.collection('users').where('age', [1], 18);

Drag options to blanks, or click blank then click option'

Aarray-contains

B!=

C==

Din

Attempts:

3 left

💡 Hint

Common Mistakes

Using unsupported operators like '!=' or 'in' incorrectly

The operator '==' is supported for simple equality checks. '!=' is not supported in Firestore queries.

4fill in blank

hard

Fill both blanks to create a compound query filtering users by age and city.

Firebase

const query = firestore.collection('users').where('age', [1], 21).where('city', [2], 'Seattle');

Drag options to blanks, or click blank then click option'

A>=

B==

C<=

D!=

Attempts:

3 left

💡 Hint

Common Mistakes

Using '!=' which is unsupported

Mixing up operators for conditions

Use '>=' to filter users aged 21 or older, and '==' to filter users in Seattle.

5fill in blank

hard

Fill all three blanks to create a Firestore query filtering products by category, price, and availability.

Firebase

const query = firestore.collection('products').where('category', [1], 'electronics').where('price', [2], 100).where('inStock', [3], true);

Drag options to blanks, or click blank then click option'

A==

B<=

D!=

Attempts:

3 left

💡 Hint

Common Mistakes

Using '!=' which is unsupported

Using wrong operators for price comparison

Use '==' to filter category and inStock status, and '<=' to filter price less than or equal to 100.

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