Query limitations and workarounds in Firebase - Mini Project: Build & Apply

Query limitations and workarounds

📖 Scenario: You are building a simple app that stores user profiles in Firebase Firestore. You want to query users by their age and city. However, Firestore has some query limitations, such as not allowing multiple inequality filters on different fields in a single query.This project will guide you to create a Firestore query setup that works around these limitations by using composite indexes and client-side filtering.

🎯 Goal: Create a Firestore query that retrieves users filtered by age and city using a composite index and client-side filtering to work around Firestore's query limitations.

📋 What You'll Learn

Create a Firestore collection reference for 'users' with sample data

Add a configuration variable for the minimum age filter

Write a Firestore query that filters users by city and age using a composite index

Add client-side filtering to further filter users by age after the query

💡 Why This Matters

🌍 Real World

Many apps need to query databases with multiple filters but face limitations in query capabilities. This project shows how to handle such cases in Firebase Firestore.

💼 Career

Understanding Firestore query limitations and workarounds is essential for cloud developers building scalable and efficient apps using Firebase.

1

Create Firestore collection reference with sample users

Create a variable called usersRef that references the Firestore collection named 'users'. Then create a list called sampleUsers with these exact user objects: { id: 'u1', age: 25, city: 'New York' }, { id: 'u2', age: 30, city: 'Los Angeles' }, { id: 'u3', age: 22, city: 'New York' }.

Firebase

# Your code here

Hint

Use firestore.collection('users') to get the collection reference.

2

Add minimum age filter configuration

Create a variable called minAge and set it to the number 23 to use as the minimum age filter.

Firebase

const usersRef = firestore.collection('users');
const sampleUsers = [
  { id: 'u1', age: 25, city: 'New York' },
  { id: 'u2', age: 30, city: 'Los Angeles' },
  { id: 'u3', age: 22, city: 'New York' }
];
# Your code here

Hint

Just create a variable minAge and assign 23.

3

Write Firestore query filtering by city and age

Create a variable called query that queries usersRef filtering where city equals 'New York' and age is greater than or equal to minAge. Use Firestore's where method twice to apply these filters.

Firebase

const usersRef = firestore.collection('users');
const sampleUsers = [
  { id: 'u1', age: 25, city: 'New York' },
  { id: 'u2', age: 30, city: 'Los Angeles' },
  { id: 'u3', age: 22, city: 'New York' }
];
const minAge = 23;
# Your code here

Hint

Chain two where calls on usersRef for city and age.

4

Add client-side filtering for age

Create a variable called filteredUsers that filters the sampleUsers list to include only users where city is 'New York' and age is greater than or equal to minAge. Use the filter method with a function that checks these conditions.

Firebase

const usersRef = firestore.collection('users');
const sampleUsers = [
  { id: 'u1', age: 25, city: 'New York' },
  { id: 'u2', age: 30, city: 'Los Angeles' },
  { id: 'u3', age: 22, city: 'New York' }
];
const minAge = 23;
const query = usersRef.where('city', '==', 'New York').where('age', '>=', minAge);
# Your code here

Hint

Use sampleUsers.filter with a function checking city and age.

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