Index creation in Ruby on Rails - Step-by-Step Execution

Concept Flow - Index creation

Start: Define index creation

↓

Write migration file

↓

Run migration

↓

Database creates index

↓

Query uses index for faster search

↓

End

This flow shows how you create an index in Rails: write a migration, run it, and then the database uses the index to speed up queries.

Execution Sample

Ruby on Rails

class AddIndexToUsersEmail < ActiveRecord::Migration[7.0]
  def change
    add_index :users, :email
  end
end

This migration adds an index on the email column of the users table to speed up email lookups.

Execution Table

Step	Action	Details	Result
1	Write migration	Define add_index on users.email	Migration file created
2	Run migration	rails db:migrate executes migration	Index created in database
3	Database updates	Index structure built on users.email	Index ready for use
4	Query execution	Search users by email	Query uses index, faster search
5	End	No more steps	Process complete

💡 Index created and ready, queries on users.email will be faster

Variable Tracker

Variable	Start	After Migration Run	After Index Creation	Final
migration_file	not created	created	created	created
database_index	none	exists on users.email	exists on users.email	exists on users.email
query_speed	normal	normal	faster	faster

Key Moments - 3 Insights

Why do we need to run the migration after writing it?

Writing the migration only creates the file. Running it applies the change to the database, actually creating the index (see execution_table step 2).

Does adding an index change the data in the table?

No, the data stays the same. The index is a separate structure that helps find data faster (see execution_table step 3).

How does the index make queries faster?

The database uses the index to quickly locate rows without scanning the whole table (see execution_table step 4).

Visual Quiz - 3 Questions

Look at the execution_table, at which step is the index actually created in the database?

A Step 2

B Step 1

C Step 4

D Step 3

💡 Hint

Check the 'Result' column in execution_table rows for when the index is created.

According to variable_tracker, what is the state of query_speed after the index creation?

A normal

B faster

C slower

D unchanged

💡 Hint

Look at the 'query_speed' row in variable_tracker after 'After Index Creation'.

If you skip running the migration, what will be the state of database_index?

A partially created

B exists on users.email

C none

D corrupted

💡 Hint

Refer to variable_tracker 'database_index' before and after migration run.

Concept Snapshot

Index creation in Rails:
- Write a migration with add_index :table, :column
- Run rails db:migrate to apply
- Database builds index structure
- Queries on that column become faster
- Data remains unchanged, only lookup speed improves

Full Transcript

In Rails, creating an index involves writing a migration file that uses add_index to specify the table and column. After writing, you run the migration with rails db:migrate, which tells the database to build the index. This index is a special structure that helps the database find rows faster when you search by that column. The data in the table does not change, only the speed of queries improves. The process ends with the index ready and queries running faster.