gitlab-org--gitlab-foss/db/migrate/20160603075128_add_has_exte...

# See http://doc.gitlab.com/ce/development/migration_style_guide.html
# for more information on how to write migrations for GitLab.

class AddHasExternalIssueTrackerToProjects < ActiveRecord::Migration[4.2]
  include Gitlab::Database::MigrationHelpers

  def change
    add_column(:projects, :has_external_issue_tracker, :boolean)
  end
end
Cache the presence of an issue_tracker at project level Using update_column to store the boolean flag to avoid any side effects with the current state of the project instance 2016-06-03 08:21:18 +00:00			`# See http://doc.gitlab.com/ce/development/migration_style_guide.html`
			`# for more information on how to write migrations for GitLab.`

Add version 4.2 to all existing migrations 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 2018-11-13 07:27:31 +00:00			`class AddHasExternalIssueTrackerToProjects < ActiveRecord::Migration[4.2]`
Cache the presence of an issue_tracker at project level Using update_column to store the boolean flag to avoid any side effects with the current state of the project instance 2016-06-03 08:21:18 +00:00			`include Gitlab::Database::MigrationHelpers`

			`def change`
			`add_column(:projects, :has_external_issue_tracker, :boolean)`
			`end`
			`end`