Creating migrations in Ruby on Rails - Performance Optimization Steps

Performance: Creating migrations

MEDIUM IMPACT

This affects the database schema update speed and the initial page load time when the app interacts with the database.

Updating database schema with migrations

Ruby on Rails

class AddDetailsToUsers < ActiveRecord::Migration[7.0]
  def change
    change_table :users do |t|
      t.text :bio
      t.integer :age
      t.boolean :admin, default: false
    end
  end
end

Combines multiple column additions into a single ALTER TABLE command, reducing table locks and downtime.

📈 Performance GainSingle table lock, reducing downtime and improving migration speed.

Updating database schema with migrations

Ruby on Rails

class AddDetailsToUsers < ActiveRecord::Migration[7.0]
  def change
    add_column :users, :bio, :text
    add_column :users, :age, :integer
    add_column :users, :admin, :boolean, default: false
  end
end

Multiple add_column statements cause separate ALTER TABLE commands, each locking the table and increasing downtime.

📉 Performance CostTriggers multiple table locks and blocks writes during migration, increasing downtime.

Performance Comparison

Pattern	Database Locks	Migration Time	App Downtime	Verdict
Multiple separate add_column calls	Multiple locks	Longer	Higher	[X] Bad
Single change_table block with multiple columns	Single lock	Shorter	Lower	[OK] Good

Rendering Pipeline

Migrations run outside the browser but affect app responsiveness by locking database tables during schema changes, which can delay API responses and page loads.

→Database Schema Update

→API Response Time

→Page Load Time

⚠️ BottleneckDatabase table locking during ALTER TABLE commands

Optimization Tips

1Batch multiple schema changes in a single migration to reduce table locks.

2Avoid running long migrations during peak traffic to minimize downtime.

3Use database-specific features like concurrent index creation when possible.

Performance Quiz - 3 Questions

What is a performance downside of running multiple separate add_column migrations instead of combining them?

A Multiple table locks increase downtime during migration

B It reduces the size of the migration file

C It improves database query speed after migration

D It automatically optimizes indexes

DevTools: Rails Console and Logs

How to check: Run migrations with verbose logging enabled and monitor the SQL commands executed; check for multiple ALTER TABLE statements.

What to look for: Look for multiple ALTER TABLE commands indicating multiple locks versus a single combined command.

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