MongoDB Find Queries | find(), findOne(), and Filtering

# CHAPTER 7

Finding and Querying Documents #

1. Introduction #

2. Learning Objectives #

• Retrieve all documents in a collection using find().

• Retrieve a single, specific document using findOne().

• Filter queries by passing a query document (the MongoDB WHERE clause).

• Shape the output by selectively returning fields using Projection.

• Format console output using .pretty().

3. Fetching Everything (find()) #

// SQL Equivalent: SELECT * FROM employees;
db.employees.find()

*Tip: If the output looks like a giant, unreadable block of text, append .pretty() to format it nicely! Example: db.employees.find().pretty() (Note: Modern versions of mongosh do this automatically).*

4. Fetching a Single Document (findOne()) #

// Just grab the very first employee in the collection
db.employees.findOne()

5. Filtering Data (The MongoDB WHERE Clause) #

// Find all employees who work in the HR department
db.employees.find({ department: "HR" })

// Find the specific employee named Alice
db.employees.findOne({ first_name: "Alice" })

// Find an employee by their exact unique ObjectId!
db.employees.findOne({ _id: ObjectId("650a2b9f8f1b2c3d4e5f6a7b") })

6. Multiple Filters (Implicit AND) #

db.employees.find({ 
    department: "Sales", 
    salary: 60000 
})

7. Projection (Selecting Specific Fields) #

In the projection document, a 1 means "Show this field", and a 0 means "Hide this field".

// Give me ALL employees, but ONLY show their first_name and department.
// SQL Equivalent: SELECT first_name, department FROM employees;
db.employees.find(
    {}, // The Query (Empty means find all)
    { first_name: 1, department: 1 } // The Projection
)

*(Notice that MongoDB always returns the id field by default! If you want to hide the ID, you must explicitly tell it: { firstname: 1, _id: 0 }).*

8. Mini Project: The E-Commerce Catalog #

db.products.find(
    // 1. The Filter (WHERE category = 'Electronics')
    { category: "Electronics" }, 
    
    // 2. The Projection (SELECT name, price)
    { name: 1, price: 1, _id: 0 } 
)

// Output:
// { "name": "Laptop", "price": 999 }
// { "name": "Headphones", "price": 199 }

9. Common Mistakes #

• String vs ObjectId Queries: If you copy an ID string from a webpage and run db.users.find({ id: "650a2b..." }), it will return nothing! The id is stored as a special binary BSON type, not a string. You must wrap it: db.users.find({ id: ObjectId("650a2b...") }).

• Mixing 1s and 0s in Projection: In a projection document, you cannot mix inclusion (1) and exclusion (0), except for the id field. You must either say "only show these 5 fields" OR "show everything except these 2 fields".

10. Best Practices #

• Never find() without Projection in Production: Just like SELECT * is a cardinal sin in SQL, executing a blind find() without a projection in Node.js or PHP will eat up massive amounts of server RAM and bandwidth. Always project only the fields your application screen actually needs to render.

11. Exercises #

1. 1. Write the command to find a single document where the username is "admin".

1. 2. Write a find() query to fetch all documents where status is "active", but use projection to ONLY return the email field (and hide the _id).

12. MongoDB Challenges #

db.users.find({ "address.city": "London" })

13. MCQ Quiz with Answers #

14. Interview Questions #

• Q: Compare and contrast the architecture of a SQL SELECT statement with a MongoDB find() method. How does MongoDB handle the SQL WHERE clause and column selection?

• Q: Explain why a query attempting to find a document by its ID string (e.g., _id: "507f1...") will fail, and how to correct the query.

15. FAQs #

16. Summary #

17. Next Chapter Recommendation #