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
18 lines
581 B
Ruby
18 lines
581 B
Ruby
# rubocop:disable all
|
|
class CreateUsersStarProjects < ActiveRecord::Migration[4.2]
|
|
DOWNTIME = false
|
|
|
|
def change
|
|
create_table :users_star_projects do |t|
|
|
t.integer :project_id, null: false
|
|
t.integer :user_id, null: false
|
|
t.timestamps null: true
|
|
end
|
|
add_index :users_star_projects, :user_id
|
|
add_index :users_star_projects, :project_id
|
|
add_index :users_star_projects, [:user_id, :project_id], unique: true
|
|
|
|
add_column :projects, :star_count, :integer, default: 0, null: false
|
|
add_index :projects, :star_count, using: :btree
|
|
end
|
|
end
|