gitlab-org--gitlab-foss/db/migrate/20161124111390_add_parent_i...

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

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

  DOWNTIME = false

  def change
    add_column(:namespaces, :parent_id, :integer)
  end
end
Add nested groups support on data level * add parent_id field to namespaces table to store relation with nested groups * create routes table to keep information about full path of every group and project * project/group lookup by full path from routes table Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com> 2016-10-31 11:00:53 +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 AddParentIdToNamespace < ActiveRecord::Migration[4.2]`
Add nested groups support on data level * add parent_id field to namespaces table to store relation with nested groups * create routes table to keep information about full path of every group and project * project/group lookup by full path from routes table Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com> 2016-10-31 11:00:53 +00:00			`include Gitlab::Database::MigrationHelpers`

			`DOWNTIME = false`

			`def change`
			`add_column(:namespaces, :parent_id, :integer)`
			`end`
			`end`