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
29 lines
721 B
Ruby
29 lines
721 B
Ruby
# rubocop:disable all
|
|
class RemoveOldMemberTables < ActiveRecord::Migration[4.2]
|
|
DOWNTIME = false
|
|
|
|
def up
|
|
drop_table :users_groups
|
|
drop_table :users_projects
|
|
end
|
|
|
|
def down
|
|
create_table :users_groups do |t|
|
|
t.integer :group_access, null: false
|
|
t.integer :group_id, null: false
|
|
t.integer :user_id, null: false
|
|
t.integer :notification_level, null: false, default: 3
|
|
|
|
t.timestamps null: true
|
|
end
|
|
|
|
create_table :users_projects do |t|
|
|
t.integer :project_access, null: false
|
|
t.integer :project_id, null: false
|
|
t.integer :user_id, null: false
|
|
t.integer :notification_level, null: false, default: 3
|
|
|
|
t.timestamps null: true
|
|
end
|
|
end
|
|
end
|