Database folder and migrations in Ruby on Rails - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ component_behavior

intermediate

What happens when you run rails db:migrate?

In a Rails project, what is the main effect of running the command rails db:migrate?

A It backs up the current database and creates a new empty database.

B It deletes all data from the database and resets the schema to the initial state.

C It generates new migration files based on changes in the models automatically.

D It applies all pending migration files in the <code>db/migrate</code> folder to update the database schema.

💡 Hint

Think about what migrations are for and what the db/migrate folder contains.

Running rails db:migrate applies all migration files that have not yet been run. These files describe changes to the database schema, such as creating or altering tables.

📝 Syntax

intermediate

Identify the correct migration syntax to add a new column

Which of the following migration snippets correctly adds a string column named username to the users table?

A add_column :username, :users, :string

B add_column :users, :username, :string

C add_column :users, :username, string

D add_column users, username, :string

💡 Hint

Remember the order of arguments for add_column is table name, column name, then type.

The correct syntax is add_column :table_name, :column_name, :type. Option B follows this exactly.

🔧 Debug

advanced

Why does this migration fail to run?

Consider this migration code:

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

Why will this migration cause an error when running rails db:migrate?

Ruby on Rails

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

A The migration version [6.1] is not supported.

B The migration class name is incorrect; it should be plural.

C The type 'integer' is not a symbol; it should be :integer.

D The method 'change' is missing a 'super' call.

💡 Hint

Check the data type argument in add_column.

In Rails migrations, data types must be symbols. Using integer without a colon causes a NameError because Ruby treats it as a variable or method name.

❓ state_output

advanced

What is the schema version after running migrations?

After running rails db:migrate, where does Rails store the current schema version number?

A In the <code>schema_migrations</code> table inside the database.

B In the <code>db/schema.rb</code> file as a Ruby constant.

C In the <code>config/database.yml</code> file under version key.

D In the <code>db/migrate</code> folder name.

💡 Hint

Think about how Rails tracks which migrations have been applied.

Rails uses a special table called schema_migrations in the database to record the version numbers of applied migrations. This helps Rails know which migrations are pending.

🧠 Conceptual

expert

Why should migration files be immutable after deployment?

In a team project, why is it important not to edit existing migration files after they have been run in production?

A Because changing migration files can cause inconsistencies between developers' databases and production, leading to errors.

B Because Rails automatically locks migration files after deployment to prevent changes.

C Because migration files are compiled into the application binary and cannot be changed.

D Because editing migration files will delete all data in the database automatically.

💡 Hint

Consider what happens if different environments have different migration histories.

Once migrations are run in production, changing them can cause mismatches in schema versions across environments. This breaks the migration system and can cause runtime errors or data loss.

Practice

1. What is the main purpose of the db/migrate folder in a Rails project?

easy

A. To store migration files that change the database structure step-by-step

B. To hold all the Ruby model files for the application

C. To keep the application configuration files

D. To store static assets like images and stylesheets

Solution

1. Step 1: Understand the role of the db/migrate folder

   This folder contains migration files that describe changes to the database schema over time.

2. Step 2: Differentiate from other folders

   Model files are in app/models, configs in config, and assets in app/assets.

3. Final Answer:

   To store migration files that change the database structure step-by-step -> Option A

4. Quick Check:

   Migration files = db/migrate folder [OK]

Hint: Migrations live in db/migrate to track database changes [OK]

Common Mistakes:

• Confusing migrations with model files
• Thinking assets or configs are in db/migrate
• Assuming db/migrate holds seed data

2. Which command correctly generates a new migration file in Rails?

easy

A. rails new migration AddAgeToUsers age:integer

B. rails generate migration AddAgeToUsers age:integer

C. rails create migration AddAgeToUsers age:integer

D. rails make migration AddAgeToUsers age:integer

Solution

1. Step 1: Recall the Rails command for generating migrations

   The correct command is rails generate migration followed by the migration name and fields.

2. Step 2: Check the options for correct syntax

   Only rails generate migration AddAgeToUsers age:integer uses the exact Rails command syntax for migration generation.

3. Final Answer:

   rails generate migration AddAgeToUsers age:integer -> Option B

4. Quick Check:

   Use rails generate migration to create migrations [OK]

Hint: Use 'rails generate migration' to create migration files [OK]

Common Mistakes:

• Using 'rails create' instead of 'rails generate'
• Confusing 'rails new' with migration commands
• Using 'rails make' which is invalid

3. Given this migration file content:

class CreateBooks < ActiveRecord::Migration[7.0]
  def change
    create_table :books do |t|
      t.string :title
      t.integer :pages
      t.timestamps
    end
  end
end

What will happen when you run rails db:migrate?

medium

A. Nothing happens because migrations only update existing tables

B. An error occurs because the migration syntax is wrong

C. The existing 'books' table will be deleted

D. A new table named 'books' with columns 'title', 'pages', and timestamps will be created

Solution

1. Step 1: Analyze the migration code

   The migration defines creating a new table called 'books' with columns 'title' (string), 'pages' (integer), and timestamps.

2. Step 2: Understand what rails db:migrate does

   It runs pending migrations, applying the changes to the database schema, here creating the 'books' table.

3. Final Answer:

   A new table named 'books' with columns 'title', 'pages', and timestamps will be created -> Option D

4. Quick Check:

   Create table migration runs successfully [OK]

Hint: Create_table migrations add new tables when migrated [OK]

Common Mistakes:

• Thinking migration deletes tables
• Assuming syntax error without checking code
• Believing migrations only update, not create

4. You wrote this migration:

class AddEmailToUsers < ActiveRecord::Migration
  def change
    add_column :users, :email, :string
  end
end

But running rails db:migrate gives an error: undefined method 'add_column'. What is the likely cause?

medium

A. The migration class should inherit from ActiveRecord::Migration[7.0] but it does

B. The migration file is missing the def change method

C. The migration class is missing the version number in inheritance

D. The migration file name does not match the class name

Solution

1. Step 1: Check the migration inheritance

   Rails 7 requires specifying the migration version in the class inheritance, e.g., ActiveRecord::Migration[7.0].

2. Step 2: Identify the error cause

   If the version is missing or incorrect, Rails may not recognize migration methods like add_column, causing the error.

3. Final Answer:

   The migration class is missing the version number in inheritance -> Option C

4. Quick Check:

   Migration version number required for method recognition [OK]

Hint: Always specify migration version in class inheritance [OK]

Common Mistakes:

• Ignoring migration version in class inheritance
• Assuming method missing means syntax error
• Not matching file name and class name

5. You want to rename a column username to login in the users table using a migration. Which migration code correctly does this?

hard

A. def change
rename_column :users, :username, :login
end

B. def change
change_column :users, :username, :login
end

C. def change
remove_column :users, :username
add_column :users, :login, :string
end

D. def change
rename_table :users, :login
end

Solution

1. Step 1: Understand the goal

   You want to rename a column, not change its type or remove and add a new one.

2. Step 2: Identify the correct migration method

   rename_column changes a column's name safely without losing data.

3. Step 3: Check options

   def change rename_column :users, :username, :login end uses rename_column :users, :username, :login, which is correct. def change change_column :users, :username, :login end wrongly uses change_column which changes type, not name. def change remove_column :users, :username add_column :users, :login, :string end removes and adds columns, which is risky. def change rename_table :users, :login end renames the whole table, not a column.

4. Final Answer:

   def change rename_column :users, :username, :login end -> Option A

5. Quick Check:

   Use rename_column to rename columns safely [OK]

Hint: Use rename_column to rename columns without data loss [OK]

Common Mistakes:

• Using change_column to rename instead of change type
• Removing and adding columns loses data
• Confusing rename_table with rename_column