0fc9f9d3e7
DB schema generated by a migration may look different in rails 4 and 5 (because rails 5 may use different default values). For this reason it's important to explicitly set for which rails version a migration was written for. See https://stackoverflow.com/questions/35929869/activerecordmigration-deprecation-warning-asks-for-rails-version-but-im-no/35930912#35930912
20 lines
544 B
Ruby
20 lines
544 B
Ruby
class AddGroupIdToMilestones < ActiveRecord::Migration[4.2]
|
|
DOWNTIME = false
|
|
|
|
def up
|
|
return if column_exists? :milestones, :group_id
|
|
|
|
change_column_null :milestones, :project_id, true
|
|
|
|
add_column :milestones, :group_id, :integer
|
|
end
|
|
|
|
def down
|
|
# We cannot rollback project_id not null constraint if there are records
|
|
# with null values.
|
|
execute "DELETE from milestones WHERE project_id IS NULL"
|
|
|
|
remove_column :milestones, :group_id
|
|
change_column :milestones, :project_id, :integer, null: false
|
|
end
|
|
end
|