Querying and filtering in Firebase - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is the purpose of querying in Firebase?

Querying in Firebase helps you find specific data by setting conditions, so you get only the information you need instead of all data.

beginner

How does filtering work in Firebase queries?

Filtering means adding rules to your query to include only data that matches those rules, like finding all users older than 18.

beginner

Which Firebase method is used to add a filter condition to a query?

The method is where(). It lets you specify a field, a comparison operator, and a value to filter data.

intermediate

Can you chain multiple filters in a Firebase query?

Yes, you can chain multiple where() methods to combine filters, like filtering users by age and city at the same time.

intermediate

What is the difference between orderBy() and where() in Firebase queries?

where() filters data by conditions, while orderBy() sorts the data by a field, like sorting users by their signup date.

Which Firebase method filters documents where a field equals a value?

A where()

B orderBy()

C limit()

D startAt()

where() is used to filter documents based on field values.

How do you filter documents where 'age' is greater than 18?

A limit(18)

B where('age', '==', 18)

C orderBy('age')

D where('age', '>', 18)

Use where('age', '>', 18) to filter for ages greater than 18.

Can you combine multiple where() filters in one query?

A Yes, by chaining multiple <code>where()</code> calls

B No, only one filter is allowed

C Only if filters are on the same field

D Only with <code>orderBy()</code>

You can chain multiple where() calls to combine filters.

What does orderBy('name') do in a Firebase query?

A Filters documents where name equals a value

B Limits results to documents with name

C Sorts documents by the 'name' field

D Starts query at document named 'name'

orderBy('name') sorts the results by the 'name' field.

Which operator is NOT valid in Firebase where() filters?

A ==

B !=

C <=

D >=

Firebase does not support the '!=' operator in where() filters.

Explain how to create a Firebase query that finds users older than 21 and sorts them by their signup date.

Think about chaining filters and sorting methods.

Describe the difference between filtering and ordering in Firebase queries and why both might be useful.

Consider how you find and display data.

Practice

1. What does the where method do in a Firestore query?

easy

A. Limits the number of documents returned

B. Sorts documents in ascending order

C. Filters documents based on a condition

D. Deletes documents matching a condition

Solution

1. Step 1: Understand the purpose of where

   The where method is used to filter documents by specifying a condition on a field.

2. Step 2: Compare with other query methods

   orderBy sorts documents, limit restricts count, and deletion is unrelated.

3. Final Answer:

   Filters documents based on a condition -> Option C

4. Quick Check:

   where = filter condition [OK]

Hint: Remember: where filters, orderBy sorts, limit restricts [OK]

Common Mistakes:

• Confusing where with orderBy
• Thinking where limits results
• Assuming where deletes data

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

easy

A. query.where('age', '>', 18)

B. query.where('age' > 18)

C. query.where('age', 'greater', 18)

D. query.where('age', '>=', '18')

Solution

1. Step 1: Check Firestore where syntax

   The correct syntax uses three arguments: field name, operator as string, and value.

2. Step 2: Validate each option

   query.where('age', '>', 18) matches correct syntax. query.where('age' > 18) misses quotes and arguments. query.where('age', 'greater', 18) uses invalid operator. query.where('age', '>=', '18') compares number to string.

3. Final Answer:

   query.where('age', '>', 18) -> Option A

4. Quick Check:

   where(field, operator, value) correct format [OK]

Hint: Use quotes around operator and field name [OK]

Common Mistakes:

• Omitting quotes around operator
• Using invalid operators like 'greater'
• Comparing number to string

3. Given this Firestore query code:

const query = collection.where('score', '>=', 50).orderBy('score').limit(3);

What will this query return?

medium

A. Top 3 documents with score less than 50

B. 3 documents with the lowest scores 50 or above

C. 3 documents with the highest scores 50 or above

D. All documents with score exactly 50

Solution

1. Step 1: Analyze the where condition

   The query filters documents with score greater than or equal to 50.

2. Step 2: Understand orderBy and limit

   Ordering by score defaults to ascending order, so lowest scores come first. Limit(3) returns first 3 documents in that order.

3. Final Answer:

   3 documents with the lowest scores 50 or above -> Option B

4. Quick Check:

   where >= 50 + orderBy ascending + limit 3 = lowest 3 scores ≥ 50 [OK]

Hint: orderBy defaults ascending unless specified [OK]

Common Mistakes:

• Assuming orderBy sorts descending by default
• Ignoring the where filter
• Thinking limit returns highest scores

4. You wrote this Firestore query:

collection.where('status', '==', 'active').orderBy('createdAt')

But it throws an error about missing index. What is the best fix?

medium

A. Add a composite index for status and createdAt

B. Remove the orderBy clause

C. Change where to filter

D. Use limit(1) to avoid indexing

Solution

1. Step 1: Understand Firestore indexing rules

   Queries with multiple conditions on different fields require composite indexes.

2. Step 2: Identify the error cause

   The query filters by status and orders by createdAt, needing a composite index.

3. Final Answer:

   Add a composite index for status and createdAt -> Option A

4. Quick Check:

   Composite index needed for where + orderBy [OK]

Hint: Create composite index for multiple fields in query [OK]

Common Mistakes:

• Removing orderBy instead of indexing
• Using invalid method 'filter'
• Thinking limit avoids index errors

5. You want to find users who are either under 18 or have a premium subscription. Which Firestore query approach is correct?

hard

A. Use a single query with where('age', '<', 18).orWhere('subscription', '==', 'premium')

B. Use orderBy on age and subscription fields

C. Use whereIn with both conditions combined

D. Use two separate queries with where and combine results in code

Solution

1. Step 1: Understand Firestore query limitations

   Firestore does not support OR queries directly in a single query.

2. Step 2: Choose correct workaround

   Run two queries separately: one for age < 18, another for subscription == premium, then merge results in code.

3. Final Answer:

   Use two separate queries with where and combine results in code -> Option D

4. Quick Check:

   Firestore lacks OR; combine queries manually [OK]

Hint: Firestore OR queries need multiple queries combined [OK]

Common Mistakes:

• Trying to use non-existent orWhere method
• Using whereIn incorrectly for OR logic
• Assuming orderBy filters data