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
21 lines
830 B
Ruby
21 lines
830 B
Ruby
class LimitsToMysql < ActiveRecord::Migration[4.2]
|
|
def up
|
|
return unless ActiveRecord::Base.configurations[Rails.env]['adapter'] =~ /^mysql/
|
|
|
|
# These columns were removed in 10.3, but this is called from two places:
|
|
# 1. A migration run after they were added, but before they were removed.
|
|
# 2. A rake task which can be run at any time.
|
|
#
|
|
# Because of item 2, we need these checks.
|
|
if column_exists?(:merge_request_diffs, :st_commits)
|
|
change_column :merge_request_diffs, :st_commits, :text, limit: 2147483647
|
|
end
|
|
|
|
if column_exists?(:merge_request_diffs, :st_diffs)
|
|
change_column :merge_request_diffs, :st_diffs, :text, limit: 2147483647
|
|
end
|
|
|
|
change_column :snippets, :content, :text, limit: 2147483647
|
|
change_column :notes, :st_diff, :text, limit: 2147483647
|
|
end
|
|
end
|