Creating migrations in Ruby on Rails - Visual Walkthrough

Concept Flow - Creating migrations

Generate migration file

↓

Edit migration file

↓

Run migration command

↓

Database schema updated

↓

Migration status checked

This flow shows how to create a migration file, edit it, run it to update the database schema, and then check the migration status.

Execution Sample

Ruby on Rails

rails generate migration AddAgeToUsers age:integer
rails db:migrate
rails db:migrate:status

This code generates a migration to add an age column to users, runs the migration, and checks migration status.

Execution Table

Step	Command/Action	Effect	Result/Output
1	rails generate migration AddAgeToUsers age:integer	Creates migration file	File db/migrate/20240610123456_add_age_to_users.rb created
2	Edit migration file (optional)	Modify change method if needed	Migration file ready with add_column :users, :age, :integer
3	rails db:migrate	Runs migration	== 20240610123456 AddAgeToUsers: migrating ====== -- add_column(:users, :age, :integer) -> 0.0012s == 20240610123456 AddAgeToUsers: migrated (0.0013s) ==
4	rails db:migrate:status	Shows migration status	up 20240610123456 AddAgeToUsers
5	Exit	All migrations up to date	No pending migrations

💡 All migrations have been applied; no pending migrations remain.

Variable Tracker

Variable	Start	After Step 1	After Step 3	Final
Migration file	None	Created with add_age_to_users.rb	Exists and ready	Applied to database schema
Database schema	Original schema	Unchanged	Updated with age column in users table	Updated schema with new column

Key Moments - 2 Insights

Why do we need to run 'rails db:migrate' after generating a migration file?

Generating a migration file only creates the instructions. Running 'rails db:migrate' actually applies those instructions to update the database schema, as shown in execution_table step 3.

What does 'rails db:migrate:status' tell us?

It shows which migrations have been applied (up) and which are pending (down). In execution_table step 4, it confirms the new migration is applied.

Visual Quiz - 3 Questions

Look at the execution table, what happens at step 1?

A Migration status is checked

B The database schema is updated

C A migration file is created

D The migration is rolled back

💡 Hint

Check the 'Effect' column in step 1 of the execution_table.

At which step does the database schema get updated?

A Step 3

B Step 4

C Step 1

D Step 5

💡 Hint

Look at the 'Result/Output' column describing the migration running.

If you skip running 'rails db:migrate', what will 'rails db:migrate:status' show?

A All migrations up to date

B The new migration marked as down (pending)

C No migrations found

D An error message

💡 Hint

Refer to the meaning of 'up' and 'down' in migration status from execution_table step 4.

Concept Snapshot

Creating migrations in Rails:
1. Generate migration file with 'rails generate migration Name'
2. Edit migration file if needed
3. Run 'rails db:migrate' to apply changes
4. Check status with 'rails db:migrate:status'
Migrations update database schema safely and track changes.

Full Transcript

Creating migrations in Rails involves generating a migration file that contains instructions to change the database schema. After generating, you can edit the file to specify the exact changes. Running 'rails db:migrate' applies these changes to the database. Finally, 'rails db:migrate:status' shows which migrations have been applied or are pending. This process helps keep the database structure organized and version controlled.

Practice

1. What is the main purpose of a migration in Rails?

easy

A. To change the database structure step-by-step

B. To write application business logic

C. To style the user interface

D. To manage user sessions

Solution

1. Step 1: Understand what migrations do

   Migrations are used to modify the database schema in a controlled way.

2. Step 2: Identify the correct purpose

   Changing database structure step-by-step matches the role of migrations.

3. Final Answer:

   To change the database structure step-by-step -> Option A

4. Quick Check:

   Migrations = Change database structure [OK]

Hint: Migrations change database structure, not app logic or UI [OK]

Common Mistakes:

• Confusing migrations with application code
• Thinking migrations handle UI or sessions

2. Which command correctly generates a migration to add a title column of type string to the posts table?

easy

A. rails generate migration AddColumn posts title:string

B. rails generate migration CreatePosts title:string

C. rails generate migration AddTitleToPosts title:string

D. rails generate migration AddTitle posts string

Solution

1. Step 1: Identify the correct migration naming pattern

   Adding a column uses 'AddColumnNameToTableName' format, here 'AddTitleToPosts'.

2. Step 2: Check the command syntax

   The correct syntax is 'rails generate migration AddTitleToPosts title:string'.

3. Final Answer:

   rails generate migration AddTitleToPosts title:string -> Option C

4. Quick Check:

   Correct migration command = rails generate migration AddTitleToPosts title:string [OK]

Hint: Use 'AddColumnToTable' naming with column:type [OK]

Common Mistakes:

• Using 'CreatePosts' instead of 'AddTitleToPosts'
• Wrong order or missing 'To' in migration name
• Incorrect column type syntax

3. Given this migration code:

class AddAgeToUsers < ActiveRecord::Migration[7.0]
  def change
    add_column :users, :age, :integer
  end
end

What happens after running rails db:migrate?

medium

A. Raises a syntax error due to missing migration version

B. Removes the 'age' column from the 'users' table

C. Creates a new 'users' table with an 'age' column

D. Adds an integer column named 'age' to the 'users' table

Solution

1. Step 1: Analyze the migration class

   The migration inherits from ActiveRecord::Migration[7.0] and defines a change method adding a column.

2. Step 2: Understand the add_column method

   It adds an integer column 'age' to the existing 'users' table.

3. Final Answer:

   Adds an integer column named 'age' to the 'users' table -> Option D

4. Quick Check:

   add_column adds column = Adds an integer column named 'age' to the 'users' table [OK]

Hint: add_column adds a new column to existing table [OK]

Common Mistakes:

• Confusing add_column with remove_column
• Thinking it creates a new table
• Missing migration version causes error (not here)

4. You wrote this migration:

class AddEmailToUsers < ActiveRecord::Migration[7.0]
  def change
    add_column :users, :email
  end
end

What is the problem when running rails db:migrate?

medium

A. Syntax error due to missing 'def up' method

B. Missing column type for 'email' causes an error

C. Migration runs successfully without issues

D. Table 'users' does not exist error

Solution

1. Step 1: Check add_column method usage

   add_column requires three arguments: table name, column name, and column type.

2. Step 2: Identify missing argument

   The migration misses the column type for 'email', causing an error.

3. Final Answer:

   Missing column type for 'email' causes an error -> Option B

4. Quick Check:

   add_column needs type argument [OK]

Hint: Always specify column type with add_column [OK]

Common Mistakes:

• Omitting column type argument
• Assuming migration runs without errors
• Confusing change method with up/down methods

5. You want to create a migration that renames the column username to login in the accounts table. Which migration code correctly does this?

hard

A. class RenameUsernameToLogin < ActiveRecord::Migration[7.0]
def change
rename_column :accounts, :username, :login
end
end

B. class RenameUsernameToLogin < ActiveRecord::Migration[7.0]
def change
change_column :accounts, :username, :login
end
end

C. class RenameUsernameToLogin < ActiveRecord::Migration[7.0]
def change
rename_table :username, :login
end
end

D. class RenameUsernameToLogin < ActiveRecord::Migration[7.0]
def change
remove_column :accounts, :username
add_column :accounts, :login, :string
end
end

Solution

1. Step 1: Identify the correct method to rename a column

   Rails provides rename_column to rename columns in a table.

2. Step 2: Check each option's method

   class RenameUsernameToLogin < ActiveRecord::Migration[7.0] def change rename_column :accounts, :username, :login end end uses rename_column correctly; class RenameUsernameToLogin < ActiveRecord::Migration[7.0] def change change_column :accounts, :username, :login end end wrongly uses change_column; class RenameUsernameToLogin < ActiveRecord::Migration[7.0] def change rename_table :username, :login end end tries to rename tables; class RenameUsernameToLogin < ActiveRecord::Migration[7.0] def change remove_column :accounts, :username add_column :accounts, :login, :string end end removes and adds columns instead of renaming.

3. Final Answer:

   Use rename_column :accounts, :username, :login in change method -> Option A

4. Quick Check:

   rename_column renames columns = class RenameUsernameToLogin < ActiveRecord::Migration[7.0] def change rename_column :accounts, :username, :login end end [OK]

Hint: Use rename_column to rename columns, not change_column [OK]

Common Mistakes:

• Using change_column instead of rename_column
• Trying to rename tables instead of columns
• Removing and adding columns instead of renaming