Read about our upcoming Code of Conduct on this issue

20170622130029_correct_protected_branches_foreign_keys.rb 1.21 KB
Newer Older
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
# See http://doc.gitlab.com/ce/development/migration_style_guide.html
# for more information on how to write migrations for GitLab.

class CorrectProtectedBranchesForeignKeys < ActiveRecord::Migration
  include Gitlab::Database::MigrationHelpers

  # Set this constant to true if this migration requires downtime.
  DOWNTIME = false

  disable_ddl_transaction!

  def up
    remove_foreign_key_without_error(:protected_branch_push_access_levels,
                                     column: :protected_branch_id)

    execute <<-EOF
    DELETE FROM protected_branch_push_access_levels
    WHERE NOT EXISTS (
      SELECT true
      FROM protected_branches
      WHERE protected_branch_push_access_levels.protected_branch_id = protected_branches.id
    )
    AND protected_branch_id IS NOT NULL
    EOF

    add_concurrent_foreign_key(:protected_branch_push_access_levels,
                               :protected_branches,
                               column: :protected_branch_id)
  end

  def down
    # Previously there was a foreign key without a CASCADING DELETE, so we'll
    # just leave the foreign key in place.
  end

  def remove_foreign_key_without_error(*args)
    remove_foreign_key(*args)
  rescue ArgumentError
  end
end