gitlab-org--gitlab-foss/db/migrate/20160119112418_add_services_default.rb

# rubocop:disable all
class AddServicesDefault < ActiveRecord::Migration[4.2]
  def up
    add_column :services, :default, :boolean, default: false

    default = quote_column_name('default')
    type    = quote_column_name('type')

    execute <<-EOF
UPDATE services
SET #{default} = true
WHERE #{type} = 'GitlabIssueTrackerService'
EOF

    add_index :services, :default
  end

  def down
    remove_column :services, :default
  end
end
Enable RuboCop for migrations Migrations shouldn't fail RuboCop checks - especially lint checks, such as the nested method check. To avoid changing code in existing migrations, add the magic comment to the top of each of them to skip that file. 2016-06-09 08:39:16 -04:00			`# rubocop:disable all`
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 02:27:31 -05:00			`class AddServicesDefault < ActiveRecord::Migration[4.2]`
Greatly improve external_issue_tracker performance This greatly improves the performance of Project#external_issue_tracker by moving most of the fields queried in Ruby to the database and letting the database handle all logic. Prior to this change the process of finding an external issue tracker was along the lines of the following: 1. Load all project services into memory. 2. Reduce the list to only services where "issue_tracker?" returns true 3. Reduce the list from step 2 to service where "default?" returns false 4. Find the first service where "activated?" returns true This has to two big problems: 1. Loading all services into memory only to reduce the list down to a single item later on is a waste of memory (and slow timing wise). 2. Calling Array#select followed by Array#reject followed by Array#find allocates extra objects when this really isn't needed. To work around this the following service fields have been moved to the database (instead of being hardcoded): * category * default This in turn means we can get the external issue tracker using the following query: SELECT * FROM services WHERE active IS TRUE AND default IS FALSE AND category = 'issue_tracker' AND project_id = XXX LIMIT 1 This coupled with memoizing the result (just as before this commit) greatly reduces the time it takes for Project#external_issue_tracker to complete. The exact reduction depends on one's environment, but locally the execution time is reduced from roughly 230 ms to only 2 ms (= a reduction of almost 180x). Fixes gitlab-org/gitlab-ce#10771 2016-01-19 07:48:07 -05:00			`def up`
			`add_column :services, :default, :boolean, default: false`

			`default = quote_column_name('default')`
			`type = quote_column_name('type')`

			`execute <<-EOF`
			`UPDATE services`
			`SET #{default} = true`
			`WHERE #{type} = 'GitlabIssueTrackerService'`
			`EOF`

			`add_index :services, :default`
			`end`

			`def down`
			`remove_column :services, :default`
			`end`
			`end`