MongoDB itself is schema-less, but Mongoose adds schema and validation support. This ensures data stored in your database follows correct format and rules.

🔹 1. Built-in Validations in Mongoose

Mongoose allows adding validations directly inside schema fields.

Example

const userSchema = new mongoose.Schema({
  name: {
    type: String,
    required: true, // must be present
    minlength: 3,
    maxlength: 50
  },
  age: {
    type: Number,
    min: 18, // minimum allowed
    max: 60
  },
  email: {
    type: String,
    required: true,
    unique: true,
    match: /^[\w-\.]+@([\w-]+\.)+[\w-]{2,4}$/ // regex for email format
  },
  createdAt: {
    type: Date,
    default: Date.now
  }
});

const User = mongoose.model("User", userSchema);

🔹 2. Custom Validation

If built-in rules are not enough, you can write your own validation function.

const productSchema = new mongoose.Schema({
  name: String,
  price: {
    type: Number,
    validate: {
      validator: function (value) {
        return value > 0; // price must be positive
      },
      message: "Price must be greater than 0"
    }
  }
});

const Product = mongoose.model("Product", productSchema);

🔹 3. Custom Schema Types

Sometimes you want to enforce specific data format.
Example → A schema type for phone numbers.

const customerSchema = new mongoose.Schema({
  phone: {
    type: String,
    validate: {
      validator: function (v) {
        return /^[0-9]{10}$/.test(v); // must be 10 digits
      },
      message: "Phone number must be 10 digits"
    }
  }
});

🎯 Real-life Example: Hotel Booking

• Validation: Guest name required, age ≥ 18, check-in date must be before check-out date.

• Custom Type: Phone number must be 10 digits, email must be valid.

const bookingSchema = new mongoose.Schema({
  guestName: { type: String, required: true },
  age: { type: Number, min: 18 },
  email: { type: String, required: true, match: /^[^@]+@[^@]+\.[^@]+$/ },
  phone: { type: String, validate: /^[0-9]{10}$/ },
  checkIn: { type: Date, required: true },
  checkOut: { type: Date, required: true }
});

// custom validation for dates
bookingSchema.path("checkOut").validate(function (value) {
  return value > this.checkIn;
}, "Check-out date must be after check-in date");

🌟 Why Validations Matter?

• Protects your database from bad data

• Saves developers from unexpected bugs later

• Ensures data integrity (clean + reliable data)

✅ Summary

Day 26

• Filtering with operators like $gt, $lt, $in

• Sorting results with .sort()

• Pagination using .skip() + .limit()

Day 27

• Built-in validations (required, min, max, match)

• Custom validations with validator functions

• Custom schema types (like phone numbers, dates, etc.)

📌 Day 26 & Day 27 – FAQ + Practice Tasks

❓ FAQ Section (Students’ Common Doubts)

1️⃣ What is the difference between find() and query operators like $gt, $lt?

👉 find() is used to fetch data from MongoDB.
👉 Query operators are conditions you pass inside find() to filter data.

Example:

Student.find({ age: { $gt: 18 } })

This means:

“Find students whose age is greater than 18”

So:

• find() → action

• $gt, $lt, $in → filtering rules

2️⃣ Can we use multiple filters together?

✅ Yes, and this is very common in real projects.

Example:

Student.find({
  age: { $gte: 18 },
  course: "Math"
})

✔ Finds students:

• age ≥ 18

• AND course = Math

MongoDB automatically applies AND condition.

3️⃣ What is the difference between sorting and filtering?

Example:

Product.find({ price: { $lt: 500 } }).sort({ price: 1 })

4️⃣ Why pagination is important? Can’t we just use find()?

❌ In small projects, yes.
❌ In real apps, NO.

Reasons:

• Too much data → slow API

• High memory usage

• Bad user experience

Pagination helps:

• Faster response

• Clean UI (page wise data)

• Scalable applications

5️⃣ What is the real meaning of skip() and limit()?

.skip(10).limit(5)

Means:

• Skip first 10 records

• Return next 5 records

Used in:

• Page 2, Page 3, Page 4… systems

6️⃣ Is validation only for frontend?

❌ No. Frontend validation can be bypassed.

✅ Backend validation is mandatory because:

• API can be called from anywhere

• Data safety is backend responsibility

Best practice:
✔ Frontend validation
✔ Backend validation (Mongoose)

7️⃣ What happens if validation fails?

Mongoose throws an error, for example:

{
  "message": "User validation failed: age must be greater than 18"
}

This error should be handled using:

• try...catch

• Express error middleware

8️⃣ Can we use custom validation in real projects?

✅ Absolutely yes.

Used for:

• Password rules

• Phone number format

• Date comparisons

• Business logic rules

9️⃣ Does validation affect database performance?

❌ Very little impact
✅ Huge benefit in data quality

So always use validations.

🔟 Are these concepts used in real companies?

💯 YES.

• Filtering → dashboards, reports

• Sorting → latest data first

• Pagination → product listing

• Validation → every form & API

🧪 Mini Exercise Tasks (Hands-On Practice)

These tasks are designed so students can practice without copying code, and actually think like developers.

🟢 Task 1: Student Filter API

Goal:

Create an API to filter students.

Requirements:

1. Create Student schema with:

   • name

   • age

   • course

   • marks

2. Create API:

   • Get students whose age > 18

   • Get students with marks ≥ 60

   • Get students from “Science” course

👉 Hint:
Use $gt, $gte

🟢 Task 2: Sorting Challenge

Goal:

Sort student records.

Requirements:

1. Sort students by:

   • marks (high → low)

   • name (A → Z)

👉 Hint:

.sort({ marks: -1 })
.sort({ name: 1 })

🟢 Task 3: Pagination Implementation

Goal:

Show students page by page.

Requirements:

1. Show only 3 students per page

2. Use URL like:

/students?page=1
/students?page=2

👉 Bonus:
Add default page if page not provided.

🟢 Task 4: Validation Practice

Goal:

Protect database using validations.

Add validations:

• name → required, min 3 characters

• age → min 18

• email → valid email format

• marks → between 0 and 100

👉 Try inserting wrong data and observe error.

🟢 Task 5: Custom Validation (Advanced)

Goal:

Create business logic validation.

Scenario:

Hotel Booking

Rules:

• checkOut date must be after checkIn

• phone number must be exactly 10 digits

👉 Implement custom validator functions.

🔥 Bonus Challenge (For Strong Students)

Build an API:

GET /students/search

Features:

• Filter by course

• Sort by marks

• Pagination enabled

• Validations applied in schema

👉 This is real-world interview-level practice.

✅ What Students Will Learn After These Tasks

✔ How real APIs handle large data
✔ Clean database design
✔ Writing production-ready schemas
✔ Thinking beyond “just CRUD”

🔔 Stay Connected

If you found this article helpful and want to receive more such beginner-friendly and industry-relevant Node JS notes, tutorials, and project ideas — 📩 Subscribe to our newsletter by entering your email below.

And if you're someone who wants to prepare for tech interviews while having a little fun and entertainment, 🎥 Don’t forget to subscribe to my YouTube channel – Knowledge Factory 22 – for regular content on tech concepts, career tips, and coding insights!

Stay curious. Keep building. 🚀