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
23 lines
610 B
Ruby
23 lines
610 B
Ruby
# See http://doc.gitlab.com/ce/development/migration_style_guide.html
|
|
# for more information on how to write migrations for GitLab.
|
|
|
|
class IssuesConfidentialNotNull < ActiveRecord::Migration[4.2]
|
|
include Gitlab::Database::MigrationHelpers
|
|
|
|
# Set this constant to true if this migration requires downtime.
|
|
DOWNTIME = false
|
|
|
|
class Issue < ActiveRecord::Base
|
|
self.table_name = 'issues'
|
|
end
|
|
|
|
def up
|
|
Issue.where('confidential IS NULL').update_all(confidential: false)
|
|
|
|
change_column_null :issues, :confidential, false
|
|
end
|
|
|
|
def down
|
|
# There's no way / point to revert this.
|
|
end
|
|
end
|