Why migrations version the database in Ruby on Rails - Quick Recap

Recall & Review

beginner

What is the main purpose of versioning migrations in Rails?

Versioning migrations helps Rails keep track of which database changes have been applied, ensuring the database schema matches the code.

beginner

How does Rails know which migrations to run when you update your app?

Rails compares the versions of migrations stored in the database with the migration files in the code to run only new migrations.

intermediate

Why is it important to have a consistent migration version history across different environments?

Consistent migration versions ensure all environments (development, test, production) have the same database structure, avoiding errors.

intermediate

What could happen if migrations were not versioned in Rails?

Without versioning, Rails wouldn't know which changes were applied, leading to possible duplicate changes or missing updates in the database.

beginner

How does Rails store migration versions internally?

Rails stores migration versions as timestamps in a special database table called schema_migrations.

What does Rails use to track which migrations have been applied?

A A database table with migration versions

B A file in the app folder

C A log in the server console

D A config setting in routes.rb

Rails uses a special table called schema_migrations to store migration versions.

Why are migration versions usually timestamps?

A To match Ruby version numbers

B To encrypt migration data

C To store user IDs

D To order migrations by creation time

Timestamps help Rails run migrations in the order they were created.

What happens if you try to run a migration that is already versioned in the database?

A Rails skips it

B Rails runs it again

C Rails deletes the database

D Rails crashes

Rails skips migrations that have already been applied to avoid duplicate changes.

Which Rails command applies new migrations to the database?

A rails server

B rails generate migration

C rails db:migrate

D rails console

The command rails db:migrate runs new migrations and updates the database schema.

What is stored in the schema_migrations table?

A User passwords

B Migration version timestamps

C Application logs

D Routes definitions

The schema_migrations table stores the timestamps of applied migrations.

Explain why Rails uses versioning for database migrations and how it helps manage database changes.

Think about how Rails knows what changes are already done.

Describe what could go wrong if migration versions were not tracked in a Rails application.

Consider the risks of losing track of database updates.

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