Scopes for reusable queries in Ruby on Rails

Introduction

Scopes help you write reusable and clear database queries in Rails models. They keep your code clean and easy to understand.

When you want to reuse a common database filter in many places.

When you want to give a name to a specific query for better readability.

When you want to chain multiple queries together easily.

When you want to keep your controller or view code simple by moving query logic to the model.

Syntax

Ruby on Rails

scope :scope_name, -> { where(condition) }

Scopes are defined inside Rails model classes.

The lambda (-> { }) delays the query execution until you call the scope.

Examples

This scope finds all records where the active column is true.

Ruby on Rails

scope :active, -> { where(active: true) }

This scope gets the 5 most recent records.

Ruby on Rails

scope :recent, -> { order(created_at: :desc).limit(5) }

This scope accepts a parameter to filter records by a given category.

Ruby on Rails

scope :by_category, ->(category) { where(category: category) }

Sample Program

This example defines three scopes in the Product model. You can call them to get products that are available, expensive, or belong to a specific brand.

Ruby on Rails

class Product < ApplicationRecord
  scope :available, -> { where(available: true) }
  scope :expensive, -> { where('price > ?', 100) }
  scope :by_brand, ->(brand) { where(brand: brand) }
end

# Usage examples:
Product.available
Product.expensive
Product.by_brand('Nike')

Important Notes

Scopes return an ActiveRecord::Relation, so you can chain them like Product.available.expensive.

Always use lambdas (-> { }) to define scopes to avoid unexpected query execution.

Summary

Scopes make queries reusable and easy to read.

Define scopes inside models using scope :name, -> { ... }.

Scopes can take parameters to customize queries.

Practice

1. What is the main purpose of using scopes in a Rails model?

easy

A. To define database table columns

B. To write controller actions

C. To create new database tables

D. To reuse common database queries easily

Solution

1. Step 1: Understand what scopes do

   Scopes are defined in models to encapsulate common queries for reuse.

2. Step 2: Identify the correct purpose

   They help avoid repeating query code by providing reusable query methods.

3. Final Answer:

   To reuse common database queries easily -> Option D

4. Quick Check:

   Scopes = reusable queries [OK]

Hint: Scopes are for reusable queries inside models [OK]

Common Mistakes:

• Confusing scopes with database schema definitions
• Thinking scopes create tables or columns
• Mixing scopes with controller logic

2. Which of the following is the correct syntax to define a scope named active that selects records with status: 'active'?

easy

A. scope :active, -> { where(status: 'active') }

B. scope active: where(status: 'active')

C. def scope :active; where(status: 'active'); end

D. scope :active { where(status: 'active') }

Solution

1. Step 1: Recall scope syntax

   Scopes use the syntax: scope :name, -> { query }.

2. Step 2: Match the correct option

   scope :active, -> { where(status: 'active') } matches this syntax exactly with a lambda returning the query.

3. Final Answer:

   scope :active, -> { where(status: 'active') } -> Option A

4. Quick Check:

   Scope syntax = scope :name, -> { ... } [OK]

Hint: Use lambda with -> { ... } for scope queries [OK]

Common Mistakes:

• Omitting the lambda syntax -> { ... }
• Using incorrect method definitions for scopes
• Missing colon before scope name

3. Given the following scopes in a Rails model:

scope :published, -> { where(published: true) }
scope :recent, -> { order(created_at: :desc) }

What will Article.published.recent.to_sql return?

medium

A. SELECT * FROM "articles" WHERE "articles"."published" = FALSE ORDER BY "articles"."created_at" ASC

B. SELECT * FROM "articles" ORDER BY "articles"."created_at" DESC WHERE "articles"."published" = TRUE

C. SELECT * FROM "articles" WHERE "articles"."published" = TRUE ORDER BY "articles"."created_at" DESC

D. SELECT * FROM "articles" WHERE "articles"."published" = TRUE

Solution

1. Step 1: Understand scope chaining

   Chaining scopes combines their queries in order: published adds a WHERE clause, recent adds ORDER BY.

2. Step 2: Analyze the SQL generated

   The SQL will filter published = true and order by created_at descending.

3. Final Answer:

   SELECT * FROM "articles" WHERE "articles"."published" = TRUE ORDER BY "articles"."created_at" DESC -> Option C

4. Quick Check:

   Chained scopes combine WHERE and ORDER BY [OK]

Hint: Chained scopes combine queries in order [OK]

Common Mistakes:

• Placing ORDER BY before WHERE in SQL
• Confusing true/false values in conditions
• Ignoring scope chaining order

4. Identify the error in this scope definition:

scope :recent, { order(created_at: :desc) }

medium

A. Missing lambda syntax -> { ... } around the query

B. Incorrect scope name format

C. Using order instead of where

D. Scope must be defined in controller, not model

Solution

1. Step 1: Check scope syntax requirements

   Scopes require a lambda (-> { ... }) to wrap the query for lazy evaluation.

2. Step 2: Identify missing lambda

   The given scope uses curly braces without the lambda arrow, causing a syntax error.

3. Final Answer:

   Missing lambda syntax -> { ... } around the query -> Option A

4. Quick Check:

   Scopes need -> { ... } [OK]

Hint: Always wrap scope queries in -> { ... } [OK]

Common Mistakes:

• Omitting the lambda arrow ->
• Defining scopes outside models
• Confusing order and where methods

5. You want to create a scope recent_active that returns records which are both active: true and created in the last 7 days. Which is the correct way to define this scope?

hard

A. scope :recent_active, -> { where(active: true).order('created_at >= 7.days.ago') }

B. scope :recent_active, -> { where(active: true).where('created_at >= ?', 7.days.ago) }

C. scope :recent_active, -> { where(active: true && created_at >= 7.days.ago) }

D. scope :recent_active, -> { where(active: true).where(created_at: 7.days.ago) }

Solution

1. Step 1: Combine conditions with where

   Use chained where calls to combine multiple conditions logically ANDed.

2. Step 2: Use correct date comparison syntax

   Use a SQL fragment with placeholder and 7.days.ago to compare dates properly.

3. Final Answer:

   scope :recent_active, -> { where(active: true).where('created_at >= ?', 7.days.ago) } -> Option B

4. Quick Check:

   Chain where with SQL and placeholders [OK]

Hint: Chain where with SQL and placeholders for complex conditions [OK]

Common Mistakes:

• Using && inside where hash instead of chaining
• Using order for filtering conditions
• Comparing created_at with exact date instead of range