Why In and not-in queries in Firebase? - Purpose & Use Cases

The Big Idea

What if you could ask your database to pick exactly what you want with just one simple question?

The Scenario

Imagine you have a list of users and you want to find only those who belong to certain groups or exclude some groups manually by checking each user one by one.

The Problem

Manually filtering users by checking each one is slow and tiring. It can cause mistakes, especially if the list is very long or changes often.

The Solution

Using 'in' queries lets you quickly ask the database to find users that belong to certain groups. This saves time and avoids errors.

Before vs After

✗ Before

for user in users:
    if user.group == 'admin' or user.group == 'editor':
        print(user)

✓ After

db.collection('users').where('group', 'in', ['admin', 'editor']).get()

What It Enables

You can easily and efficiently filter data by multiple values without writing complex code or checking each item yourself.

Real Life Example

A chat app shows messages only from selected chat rooms by querying messages where the room ID is in a list of active rooms.

Key Takeaways

Manual filtering is slow and error-prone.

'In' queries let the database do the filtering fast.

This makes your app faster and your code simpler.

Practice

1.

What does the in query do in Firebase Firestore?

easy

A. Finds documents where a field is null

B. Finds documents where a field does not exist

C. Finds documents where a field matches exactly one value only

D. Finds documents where a field matches any value in a given list

Solution

1. Step 1: Understand the purpose of in query

   The in query checks if a field's value matches any value from a list of values.

2. Step 2: Compare with other options

   Null fields and non-existent fields describe different query types, while limiting to exactly one value is incorrect for in.

3. Final Answer:

   Finds documents where a field matches any value in a given list -> Option D

4. Quick Check:

   in query = matches any value in list [OK]

Hint: Remember: 'in' means match any value from a list [OK]

Common Mistakes:

• Confusing 'in' with 'not-in' query
• Thinking 'in' matches only one value
• Assuming 'in' checks for field existence

2.

Which of the following is the correct syntax for a not-in query in Firestore?

db.collection('users').where('age', ___, [18, 21, 25])

easy

A. 'notin'

B. 'not-in'

C. 'not_in'

D. 'nin'

Solution

1. Step 1: Recall Firestore query operators

   Firestore uses exact strings for operators; the correct operator for excluding values is 'not-in'.

2. Step 2: Check each option's validity

   'notin', 'not_in', and 'nin' are invalid syntax and will cause errors.

3. Final Answer:

   'not-in' -> Option B

4. Quick Check:

   Correct operator syntax = 'not-in' [OK]

Hint: Use exact operator strings: 'not-in' with hyphen [OK]

Common Mistakes:

• Using 'notin' or 'not_in' instead of 'not-in'
• Missing quotes around operator
• Using unsupported operators like 'nin'

3.

Given this Firestore query:

db.collection('products').where('category', 'in', ['books', 'games']).get()

Which documents will be returned?

medium

A. Documents where category is either 'books' or 'games'

B. Documents where category is not 'books' or 'games'

C. Documents where category is exactly 'booksgames'

D. All documents regardless of category

Solution

1. Step 1: Understand the 'in' query behavior

   The query filters documents where the 'category' field matches any value in the list ['books', 'games'].

2. Step 2: Analyze each option

   Documents where category is either 'books' or 'games' matches the query logic. Documents where category is not 'books' or 'games' is the opposite. Documents where category is exactly 'booksgames' is a concatenation, which is incorrect. All documents regardless of category ignores the filter.

3. Final Answer:

   Documents where category is either 'books' or 'games' -> Option A

4. Quick Check:

   'in' query returns matching values in list [OK]

Hint: Think: 'in' means any value inside the list [OK]

Common Mistakes:

• Confusing 'in' with 'not-in'
• Assuming concatenation of list values
• Ignoring the filter and expecting all documents

4.

What is wrong with this Firestore query?

db.collection('orders').where('status', 'not-in', ['shipped', 'delivered', 'pending', 'cancelled', 'new', 'processing', 'confirmed', 'refunded', 'returned', 'failed', 'on_hold']).get()

It throws an error. Why?

medium

A. The 'not-in' operator cannot be used with more than 10 values in the list

B. The field 'status' does not exist in the collection

C. The 'not-in' operator is not supported in Firestore

D. The list has more than 20 values, exceeding Firestore limits

Solution

1. Step 1: Recall Firestore limits on 'not-in' queries

   Firestore limits 'not-in' and 'in' queries to a maximum of 10 values in the list.

2. Step 2: Count values in the list

   The list has 11 values, exceeding the 10-value limit for 'not-in' queries.

3. Step 3: Consider other options

   The list has more than 20 values, exceeding Firestore limits is incorrect because the list has 11 values. The 'not-in' operator is not supported in Firestore is wrong because 'not-in' is supported. The field 'status' does not exist in the collection is unrelated to the error.

4. Final Answer:

   The 'not-in' operator cannot be used with more than 10 values in the list -> Option A

5. Quick Check:

   'not-in' max 10 values limit causes errors [OK]

Hint: Check list size: 'not-in' max 10 values allowed [OK]

Common Mistakes:

• Assuming 'not-in' supports unlimited list size
• Blaming field existence without checking
• Confusing 'not-in' support in Firestore

5.

You want to find all users whose role is neither 'admin' nor 'moderator' nor 'guest'. Which Firestore query is correct?

hard

A. db.collection('users').where('role', '!=', ['admin', 'moderator', 'guest']).get()

B. db.collection('users').where('role', 'in', ['admin', 'moderator', 'guest']).get()

C. db.collection('users').where('role', 'not-in', ['admin', 'moderator', 'guest']).get()

D. db.collection('users').where('role', 'not-in', 'admin,moderator,guest').get()

Solution

1. Step 1: Understand the requirement

   You want users whose role is NOT any of the listed roles. This means excluding those roles.

2. Step 2: Choose the correct operator and syntax

   The 'not-in' operator excludes documents with any value in the list. db.collection('users').where('role', 'not-in', ['admin', 'moderator', 'guest']).get() uses correct syntax with a list. db.collection('users').where('role', 'in', ['admin', 'moderator', 'guest']).get() includes only those roles, which is opposite. db.collection('users').where('role', '!=', ['admin', 'moderator', 'guest']).get() uses '!=' which does not accept lists. db.collection('users').where('role', 'not-in', 'admin,moderator,guest').get() uses a string instead of a list, which is invalid.

3. Final Answer:

   db.collection('users').where('role', 'not-in', ['admin', 'moderator', 'guest']).get() -> Option C

4. Quick Check:

   Use 'not-in' with list to exclude multiple values [OK]

Hint: Use 'not-in' with array to exclude multiple values [OK]

Common Mistakes:

• Using '!=' with a list instead of a single value
• Passing a string instead of an array for 'not-in'
• Using 'in' instead of 'not-in' for exclusion