Why Scopes for reusable queries in Ruby on Rails? - Purpose & Use Cases

The Big Idea

Discover how a tiny change can save you hours of repetitive work and bugs!

The Scenario

Imagine you have a website with thousands of users, and you want to find all active users or users created in the last week. You write the same complex database query again and again in different parts of your code.

The Problem

Manually repeating queries is tiring and risky. If you make a mistake or want to change the query, you must update every place it appears. This leads to bugs and wasted time.

The Solution

Scopes let you define a query once inside your model. Then you can reuse it everywhere by calling a simple method. This keeps your code clean, consistent, and easy to update.

Before vs After

✗ Before

User.where(active: true).order(created_at: :desc)
User.where(active: true).order(created_at: :desc).limit(10)

✓ After

class User < ApplicationRecord
  scope :active, -> { where(active: true).order(created_at: :desc) }
end

User.active
User.active.limit(10)

What It Enables

Scopes make your queries reusable and your code easier to read and maintain.

Real Life Example

In a blog app, you can create a scope to get all published posts. Then anywhere you need published posts, just call Post.published instead of rewriting the query.

Key Takeaways

Manually repeating queries causes errors and extra work.

Scopes let you write queries once and reuse them easily.

This improves code clarity, consistency, and maintenance.