Adding and removing columns in Ruby on Rails - Practice Problems & Coding Challenges

Challenge - 5 Problems

📝 Syntax

intermediate

Correct syntax for adding a column in Rails migration

Which option correctly adds a new column named age of type integer to the users table in a Rails migration?

Ruby on Rails

class AddAgeToUsers < ActiveRecord::Migration[7.0]
  def change
    # Add column here
  end
end

A add_column :users, :age, :integer

B add_column :age, :users, :integer

C add_column :users, :age, integer

D add_column users, :age, :integer

💡 Hint

Remember the order: table name, column name, then type, all symbols except type must be symbols.

The add_column method requires the table name first, then the column name, and then the type as a symbol. Option A follows this pattern correctly.

Option A swaps table and column names, causing an error.

Option A misses the colon before integer, causing a syntax error.

Option A misses the colon before users, causing a syntax error.

❓ component_behavior

intermediate

Effect of removing a column in Rails migration

After running this migration, what will happen to the email column in the customers table?

Ruby on Rails

class RemoveEmailFromCustomers < ActiveRecord::Migration[7.0]
  def change
    remove_column :customers, :email, :string
  end
end

A The <code>email</code> column will be set to NULL but not removed.

B The <code>email</code> column will be renamed to <code>string</code>.

C The migration will fail because <code>remove_column</code> does not accept a type argument.

D The <code>email</code> column will be deleted from the <code>customers</code> table.

💡 Hint

Think about what remove_column does in Rails migrations.

The remove_column method deletes the specified column from the table. The type argument is optional but allowed for safety.

Option D is incorrect because it does not rename columns.

Option D is incorrect because the type argument is allowed but optional.

Option D is incorrect because the column is removed, not just nulled.

🔧 Debug

advanced

Identify the error in this migration removing a column

What error will this migration raise when run?

Ruby on Rails

class RemoveStatusFromOrders < ActiveRecord::Migration[7.0]
  def change
    remove_column :orders, :status
  end
end

A No error, migration runs successfully and removes the column.

B RuntimeError because remove_column requires a block.

C SyntaxError due to missing colon before :status.

D ArgumentError because the column type is missing in remove_column call.

💡 Hint

Check the Rails documentation for remove_column method signature.

The remove_column method can be called with just the table name and column name. The type argument is optional.

Option A is incorrect because the type is optional.

Option A is incorrect because the syntax is correct.

Option A is incorrect because remove_column does not require a block.

❓ state_output

advanced

State of the database after adding and removing columns

Given these two migrations run in order, what columns will the products table have?

Ruby on Rails

class AddDescriptionToProducts < ActiveRecord::Migration[7.0]
  def change
    add_column :products, :description, :text
  end
end

class RemovePriceFromProducts < ActiveRecord::Migration[7.0]
  def change
    remove_column :products, :price, :decimal
  end
end

A The <code>products</code> table will have neither <code>description</code> nor <code>price</code> columns.

B The <code>products</code> table will have both <code>description</code> and <code>price</code> columns.

C The <code>products</code> table will have the <code>description</code> column added and the <code>price</code> column removed.

D The migrations will fail because you cannot add and remove columns in separate migrations.

💡 Hint

Think about what each migration does and that migrations run in order.

The first migration adds the description column.

The second migration removes the price column.

Both migrations run successfully and change the table accordingly.

Option C is incorrect because price is removed.

Option C is incorrect because description is added.

Option C is incorrect because Rails supports multiple migrations modifying the same table.

🧠 Conceptual

expert

Understanding reversible migrations with add_column and remove_column

Which statement best describes how Rails handles the change method when using add_column and remove_column in a migration?

A Rails can reverse both <code>add_column</code> and <code>remove_column</code> automatically without any extra code.

B Rails automatically knows how to reverse <code>add_column</code> by removing the column, but cannot reverse <code>remove_column</code> without extra information.

C Rails cannot reverse either <code>add_column</code> or <code>remove_column</code> automatically; you must write separate <code>up</code> and <code>down</code> methods.

D Rails reverses <code>remove_column</code> by adding the column back with default values, but cannot reverse <code>add_column</code>.

💡 Hint

Think about what information Rails needs to reverse a migration.

Rails can reverse add_column automatically by removing the added column.

However, remove_column cannot be reversed automatically because Rails does not know the column's type or options unless explicitly provided.

Therefore, to make remove_column reversible, you must provide extra information or write separate up and down methods.