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
24 lines
952 B
Ruby
24 lines
952 B
Ruby
# rubocop:disable all
|
|
class AddVisibilityLevelToSnippet < ActiveRecord::Migration[4.2]
|
|
include Gitlab::Database::MigrationHelpers
|
|
|
|
def up
|
|
add_column :snippets, :visibility_level, :integer, :default => 0, :null => false
|
|
|
|
execute("UPDATE snippets SET visibility_level = #{Gitlab::VisibilityLevel::PRIVATE} WHERE private = #{true_value}")
|
|
execute("UPDATE snippets SET visibility_level = #{Gitlab::VisibilityLevel::INTERNAL} WHERE private = #{false_value}")
|
|
|
|
add_index :snippets, :visibility_level
|
|
|
|
remove_column :snippets, :private
|
|
end
|
|
|
|
def down
|
|
add_column :snippets, :private, :boolean, :default => false, :null => false
|
|
|
|
execute("UPDATE snippets SET private = #{false_value} WHERE visibility_level = #{Gitlab::VisibilityLevel::INTERNAL}")
|
|
execute("UPDATE snippets SET private = #{true_value} WHERE visibility_level = #{Gitlab::VisibilityLevel::PRIVATE}")
|
|
|
|
remove_column :snippets, :visibility_level
|
|
end
|
|
end
|