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
17 lines
866 B
Ruby
17 lines
866 B
Ruby
# This migration will create one row of NotificationSetting for each Member row
|
|
# It can take long time on big instances.
|
|
#
|
|
# This migration can be done online but with following effects:
|
|
# - during migration some users will receive notifications based on their global settings (project/group settings will be ignored)
|
|
# - its possible to get duplicate records for notification settings since we don't create uniq index yet
|
|
#
|
|
class MigrateNewNotificationSetting < ActiveRecord::Migration[4.2]
|
|
def up
|
|
timestamp = Time.now.strftime('%F %T')
|
|
execute "INSERT INTO notification_settings ( user_id, source_id, source_type, level, created_at, updated_at ) SELECT user_id, source_id, source_type, notification_level, '#{timestamp}', '#{timestamp}' FROM members WHERE user_id IS NOT NULL"
|
|
end
|
|
|
|
def down
|
|
execute "DELETE FROM notification_settings"
|
|
end
|
|
end
|