While I don't use this feature, there are developers who do. It's useful when running migrations and changing branches. I'm raising an `ActiveRecord::IrreversibleMigration` exception in every `drop_table` migration because these migrations were all done before version 1.0.0, and so making all of them reversible would be too much work for little benefit.
21 lines
778 B
Ruby
21 lines
778 B
Ruby
class RefactorVerificationColumns < ActiveRecord::Migration[4.2]
|
|
def change
|
|
rename_column :users, :sms_verification_code, :sms_confirmation_code
|
|
|
|
remove_column :users, :sms_verified_at, :datetime
|
|
remove_column :users, :email_verified_at, :datetime
|
|
remove_column :users, :email_for_verification, :string
|
|
remove_column :users, :verified_user_sms_verified_at, :datetime
|
|
add_column :users, :verified_at, :datetime
|
|
|
|
remove_column :users, :phone, :string
|
|
add_column :users, :unconfirmed_phone, :string
|
|
add_column :users, :confirmed_phone, :string
|
|
|
|
remove_column :users, :letter_requested, :boolean, default: false
|
|
add_column :users, :letter_requested_at, :datetime
|
|
|
|
rename_column :users, :sms_tries, :sms_confirmation_tries
|
|
end
|
|
end
|