Changing column types in Ruby on Rails - Practice Problems & Coding Challenges

Challenge - 5 Problems

📝 Syntax

intermediate

Correct syntax for changing a column type in Rails migration

Which option correctly changes the column type of age from integer to string in a Rails migration?

Ruby on Rails

class ChangeAgeTypeInUsers < ActiveRecord::Migration[7.0]
  def change
    # change column type here
  end
end

A change_column :age, :users, :string

B change_column :users, :age, :string

C change_column_type :age, :users, :string

D change_column_type :users, :age, :string

💡 Hint

Remember the order: table name, column name, then new type.

The change_column method takes the table name first, then the column name, and finally the new type.

Options A, B, and C use incorrect method names or argument orders.

❓ component_behavior

intermediate

Effect of changing column type on existing data

What happens to existing data in the price column when you change its type from integer to string using change_column in Rails migration?

A Existing integer values are converted to strings preserving their values

B Existing data is deleted and the column is emptied

C Migration fails with a type mismatch error

D Existing data remains as integers and causes runtime errors

💡 Hint

Think about how databases handle type casting during column changes.

When changing a column type from integer to string, the database converts existing integer values to their string representations.

Data is preserved but converted.

🔧 Debug

advanced

Identify the error in this migration changing column type

What error will this migration raise when run?

class ChangeActiveToBooleanInUsers < ActiveRecord::Migration[7.0]
  def change
    change_column :users, :active, :boolean, default: false
  end
end

Ruby on Rails

class ChangeActiveToBooleanInUsers < ActiveRecord::Migration[7.0]
  def change
    change_column :users, :active, :boolean, default: false
  end
end

A ActiveRecord::StatementInvalid: invalid type for default value

B ArgumentError: unknown keyword: default

C SyntaxError: unexpected keyword_end

D No error, migration runs successfully

💡 Hint

Check the allowed options for change_column method.

No error. The change_column method accepts default as an option.

To change only the default without changing type, use change_column_default separately.

❓ state_output

advanced

Resulting schema after changing column type with null constraint

After running this migration, what will be the null constraint on the email column?

class ChangeEmailTypeInUsers < ActiveRecord::Migration[7.0]
  def change
    change_column :users, :email, :text, null: false
  end
end

Ruby on Rails

class ChangeEmailTypeInUsers < ActiveRecord::Migration[7.0]
  def change
    change_column :users, :email, :text, null: false
  end
end

A The <code>email</code> column will NOT allow null values

B The <code>email</code> column will allow null values

C The migration will fail with an error about null constraint

D The null constraint remains unchanged from before migration

💡 Hint

Does change_column support changing null constraints directly?

The change_column method supports the null option, setting the column to NOT allow null values.

For nullability-only changes, prefer change_column_null for better reversibility across databases.

🧠 Conceptual

expert

Best practice for changing column type with data migration

You need to change a column type from string to integer but existing data may not convert cleanly. What is the best approach to handle this safely in Rails migrations?

A Drop the table and recreate it with the new column type

B Use <code>change_column</code> directly and fix data errors later

C Create a new column with the new type, migrate data manually, then remove old column

D Change the column type in the database manually outside Rails

💡 Hint

Think about data safety and rollback ability.

Changing column types directly can cause data loss or errors if data doesn't convert cleanly.

Best practice is to add a new column, migrate and clean data manually, then remove the old column.

This approach is safer and reversible.

Practice

1.

What is the primary Rails method used to change the type of an existing database column in a migration?

easy

A. change_column

B. rename_column

C. add_column

D. remove_column

Solution

1. Step 1: Understand migration methods

   Rails migrations provide specific methods for altering tables. add_column adds new columns, remove_column deletes columns, and rename_column changes column names.

2. Step 2: Identify method for changing column type

   The method change_column is designed to change the type of an existing column without removing it.

3. Final Answer:

   change_column -> Option A

4. Quick Check:

   Change column type = change_column [OK]

Hint: Use change_column to modify column types in migrations [OK]

Common Mistakes:

• Confusing change_column with rename_column
• Trying to use add_column to change type
• Using remove_column instead of changing type

2.

Which of the following is the correct syntax to change a column named price to type decimal with precision 8 and scale 2 in a Rails migration?

class ChangePriceTypeInProducts < ActiveRecord::Migration[7.0]
  def change
    ?
  end
end

easy

A. change_column :products, :price, :decimal, precision: 8, scale: 2

B. change_column :products, :price, :decimal(8,2)

C. change_column :products, :price, :decimal, {precision: 8, scale: 2}

D. change_column :products, :price, :decimal, precision => 8, scale => 2

Solution

1. Step 1: Review change_column syntax

   The correct syntax uses symbol keys for options: change_column(table, column, type, options). Options like precision and scale are passed as keyword arguments.

2. Step 2: Identify correct option format

   change_column :products, :price, :decimal, precision: 8, scale: 2 correctly uses precision: 8, scale: 2 as keyword arguments. change_column :products, :price, :decimal(8,2) uses invalid syntax. change_column :products, :price, :decimal, {precision: 8, scale: 2} uses a hash but without keyword arguments. change_column :products, :price, :decimal, precision => 8, scale => 2 uses hash rockets which is invalid in this context.

3. Final Answer:

   change_column :products, :price, :decimal, precision: 8, scale: 2 -> Option A

4. Quick Check:

   Keyword args for options = change_column :products, :price, :decimal, precision: 8, scale: 2 [OK]

Hint: Use keyword arguments for options in change_column [OK]

Common Mistakes:

• Using parentheses in type declaration like :decimal(8,2)
• Passing options as a hash without keywords
• Using old hash rocket syntax in options

3.

Given this migration snippet, what will be the new type of the age column after running it?

class ChangeAgeTypeInUsers < ActiveRecord::Migration[7.0]
  def change
    change_column :users, :age, :string
  end
end

medium

A. integer

B. boolean

C. string

D. float

Solution

1. Step 1: Read the change_column call

   The method call changes the age column in the users table to type :string.

2. Step 2: Understand the effect

   After running the migration, the age column will store string values instead of its previous type.

3. Final Answer:

   string -> Option C

4. Quick Check:

   change_column to :string = string [OK]

Hint: Look at the third argument of change_column for new type [OK]

Common Mistakes:

• Assuming the type stays the same
• Confusing column name with type
• Thinking change_column renames columns

4.

What is wrong with this migration code that tries to change a column type?

class ChangeActiveToBooleanInUsers < ActiveRecord::Migration[7.0]
  def change
    change_column :users, :active, 'boolean'
  end
end

medium

A. The column name should be a string, not a symbol

B. The type should be a symbol, not a string

C. change_column cannot change to boolean type

D. The migration class name is invalid

Solution

1. Step 1: Check argument types in change_column

   The method expects the type argument as a symbol, e.g., :boolean, not a string.

2. Step 2: Identify the error

   Using a string like 'boolean' will cause a syntax or runtime error because Rails expects symbols for types.

3. Final Answer:

   The type should be a symbol, not a string -> Option B

4. Quick Check:

   Type argument must be symbol = The type should be a symbol, not a string [OK]

Hint: Use symbols (e.g., :boolean) for types in change_column [OK]

Common Mistakes:

• Passing type as a string instead of symbol
• Thinking change_column can't handle boolean
• Misnaming migration class

5.

You want to change a column rating from integer to decimal with precision 3 and scale 1, but keep existing data safe. Which approach is best?

hard

A. Use change_column :table, :rating, :decimal, precision: 3, scale: 1 directly in one migration

B. Change the column type in the database manually without migration

C. Drop the column and add a new decimal column with the same name

D. Create a new decimal column, copy data with conversion, then remove old column and rename new one

Solution

1. Step 1: Understand risks of direct change_column

   Directly changing column type can cause data loss or errors if existing data doesn't fit new type.

2. Step 2: Use safe migration strategy

   Creating a new column, copying data with conversion, then removing old column and renaming new one ensures data safety and rollback ability.

3. Final Answer:

   Create a new decimal column, copy data with conversion, then remove old column and rename new one -> Option D

4. Quick Check:

   Safe type change = create-copy-rename [OK]

Hint: Avoid direct type change; copy data safely first [OK]

Common Mistakes:

• Directly changing type risking data loss
• Dropping column without backup
• Changing DB manually without migration