Why migrations version the database in Ruby on Rails - Challenge Your Understanding

Challenge - 5 Problems

🧠 Conceptual

intermediate

Why does Rails keep track of migration versions?

Rails migrations have a version number stored in the database. Why is this versioning important?

A It helps Rails know which migrations have already run to avoid running them again.

B It stores the database schema size to optimize queries automatically.

C It tracks user access levels for database security.

D It records the number of rows in each table for reporting.

💡 Hint

Think about how Rails applies changes step-by-step without repeating work.

Rails stores migration versions to track which changes have been applied. This prevents running the same migration twice, which could cause errors or duplicate changes.

❓ component_behavior

intermediate

What happens if a migration version is missing in the database?

If a migration file exists but its version is not recorded in the database, what will Rails do when running migrations?

A Rails will raise an error and stop the migration process.

B Rails will skip the migration assuming it is already applied.

C Rails will run that migration to apply its changes.

D Rails will delete the migration file automatically.

💡 Hint

Consider how Rails decides which migrations to apply.

If a migration version is not found in the database, Rails treats it as new and runs it to update the schema.

🔧 Debug

advanced

Why does running the same migration twice cause an error?

Given a migration that adds a column, what error occurs if Rails tries to run it twice and why?

Ruby on Rails

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

A ActiveRecord::DuplicateMigrationError because the migration version is duplicated.

B ActiveRecord::StatementInvalid because the column already exists in the database.

C No error, Rails ignores duplicate migrations automatically.

D SyntaxError because the migration file is invalid.

💡 Hint

Think about what happens when you try to add a column that is already there.

Running the same migration twice tries to add a column that already exists, causing a database error.

📝 Syntax

advanced

Which migration version format is correct in Rails?

Rails migration files start with a timestamp version. Which of these is the correct format for a migration version?

A 20240612123456

B version_2024_06_12

C 12-06-2024-123456

D migration20240612

💡 Hint

Look for a continuous numeric timestamp format.

Rails uses a timestamp format YYYYMMDDHHMMSS as the migration version to order migrations chronologically.

❓ state_output

expert

What is the state of the schema_migrations table after running migrations?

After running three migrations with versions 20240612120000, 20240612121500, and 20240612123000, what will the schema_migrations table contain?

A Rows with migration names instead of versions

B One row with the latest version: 20240612123000

C No rows because migrations do not update this table

D Three rows with versions: 20240612120000, 20240612121500, 20240612123000

💡 Hint

Think about how Rails tracks all applied migrations, not just the latest.

The schema_migrations table stores each migration version that has been applied to the database as a separate row.