Why migrations version the database in Ruby on Rails

Introduction

Migrations keep track of changes to the database so Rails knows what has been done and what still needs to be done.

When adding a new table to store user data

When changing a column type in an existing table

When removing a column that is no longer needed

When fixing a mistake in a previous database change

When sharing database changes with other developers

Syntax

Ruby on Rails

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

Each migration file has a version number based on timestamp to order changes.

Rails uses this version to know which migrations have run and which are pending.

Examples

This migration creates a users table and is identified by the timestamp 20230610120000.

Ruby on Rails

20230610120000_create_users.rb
class CreateUsers < ActiveRecord::Migration[7.0]
  def change
    create_table :users do |t|
      t.string :name
    end
  end
end

This migration adds an email column to users and runs after the previous one because of its later timestamp.

Ruby on Rails

20230611130000_add_email_to_users.rb
class AddEmailToUsers < ActiveRecord::Migration[7.0]
  def change
    add_column :users, :email, :string
  end
end

Sample Program

This example shows creating a books table with title and author columns. Rails uses the migration's timestamp version to track it.

Ruby on Rails

# Run in terminal:
# rails generate migration CreateBooks title:string author:string
# rails db:migrate

# Migration file example:
class CreateBooks < ActiveRecord::Migration[7.0]
  def change
    create_table :books do |t|
      t.string :title
      t.string :author
    end
  end
end

# After running rails db:migrate, Rails records the migration version in schema_migrations table.

Important Notes

Always keep migrations in order by timestamp to avoid conflicts.

Never edit old migrations after they have been run in production; create new migrations instead.

Summary

Migrations version the database to track changes over time.

This helps Rails know which changes are applied and which are pending.

Versioning prevents confusion and keeps database structure consistent.

Practice

1. Why does Rails use version numbers in database migrations?

easy

A. To track which migrations have been applied to the database

B. To speed up database queries

C. To store user data securely

D. To create backups automatically

Solution

1. Step 1: Understand migration purpose

   Migrations change the database structure over time.

2. Step 2: Role of version numbers

   Version numbers help Rails know which migrations ran and which are pending.

3. Final Answer:

   To track which migrations have been applied to the database -> Option A

4. Quick Check:

   Migration versioning = tracking applied changes [OK]

Hint: Version numbers track applied migrations, not data or speed [OK]

Common Mistakes:

• Thinking version numbers speed up queries
• Confusing versioning with data storage
• Assuming version numbers create backups

2. Which of the following is the correct way Rails names migration version numbers?

easy

A. A user-defined name without numbers

B. A random string of letters

C. A timestamp prefix like 20240612123456_create_users.rb

D. A hash of the migration content

Solution

1. Step 1: Identify Rails migration naming

   Rails uses timestamps to order migrations chronologically.

2. Step 2: Confirm correct format

   Migration files start with a timestamp like 20240612123456 followed by a descriptive name.

3. Final Answer:

   A timestamp prefix like 20240612123456_create_users.rb -> Option C

4. Quick Check:

   Migration version = timestamp prefix [OK]

Hint: Look for timestamp prefix in migration filenames [OK]

Common Mistakes:

• Thinking version is random letters
• Ignoring the timestamp format
• Assuming user names migrations without numbers

3. Given these migrations applied in order:
20240601010101_create_users.rb
20240602020202_add_email_to_users.rb
What will Rails do if you run rails db:migrate again without new migrations?

medium

A. It will apply all migrations again

B. It will skip migrations because they are already applied

C. It will delete the database

D. It will raise an error about duplicate migrations

Solution

1. Step 1: Understand migration tracking

   Rails records applied migrations by their version numbers in a special table.

2. Step 2: Behavior on re-running migrations

   If no new migrations exist, Rails skips already applied ones to avoid duplicate changes.

3. Final Answer:

   It will skip migrations because they are already applied -> Option B

4. Quick Check:

   Applied migrations are skipped on rerun [OK]

Hint: Rails skips migrations already recorded as applied [OK]

Common Mistakes:

• Thinking migrations run twice
• Expecting database deletion
• Assuming errors on duplicate versions

4. You created a migration file but forgot to update its version timestamp. What problem will this cause when running rails db:migrate?

medium

A. Rails will ignore the migration because the version conflicts

B. Rails will apply the migration twice

C. Rails will raise a syntax error

D. Rails will rename the migration automatically

Solution

1. Step 1: Understand version uniqueness

   Each migration version must be unique to track changes properly.

2. Step 2: Effect of duplicate version

   If two migrations share the same version, Rails ignores the second to avoid conflicts.

3. Final Answer:

   Rails will ignore the migration because the version conflicts -> Option A

4. Quick Check:

   Duplicate versions cause ignored migrations [OK]

Hint: Duplicate timestamps cause migrations to be ignored [OK]

Common Mistakes:

• Expecting automatic renaming
• Thinking Rails applies duplicates
• Assuming syntax errors from version conflicts

5. You have two developers creating migrations simultaneously. Developer A creates 20240612120000_add_age_to_users.rb and Developer B creates 20240612120000_add_status_to_users.rb. What issue arises and how should it be resolved?

hard

A. Rails will run only the first migration and ignore the second permanently

B. Rails merges both migrations automatically without issues

C. One migration overwrites the other silently

D. Both migrations have the same version causing conflicts; rename one with a unique timestamp

Solution

1. Step 1: Identify version conflict

   Both migrations share the exact same timestamp version, which must be unique.

2. Step 2: Resolve conflict

   To fix, rename one migration file with a different timestamp so Rails can track both separately.

3. Final Answer:

   Both migrations have the same version causing conflicts; rename one with a unique timestamp -> Option D

4. Quick Check:

   Unique timestamps prevent migration conflicts [OK]

Hint: Ensure unique timestamps when multiple developers create migrations [OK]

Common Mistakes:

• Assuming Rails merges migrations automatically
• Thinking one migration overwrites the other silently
• Believing Rails ignores second migration permanently