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
22 lines
644 B
Ruby
22 lines
644 B
Ruby
# rubocop:disable Migration/Timestamps
|
|
class CreateUserChatNamesTable < ActiveRecord::Migration[4.2]
|
|
include Gitlab::Database::MigrationHelpers
|
|
|
|
DOWNTIME = false
|
|
|
|
def change
|
|
create_table :chat_names do |t|
|
|
t.integer :user_id, null: false
|
|
t.integer :service_id, null: false
|
|
t.string :team_id, null: false
|
|
t.string :team_domain
|
|
t.string :chat_id, null: false
|
|
t.string :chat_name
|
|
t.datetime :last_used_at
|
|
t.timestamps null: false
|
|
end
|
|
|
|
add_index :chat_names, [:user_id, :service_id], unique: true
|
|
add_index :chat_names, [:service_id, :team_id, :chat_id], unique: true
|
|
end
|
|
end
|