From cb4ee4b1314de77554db10645c5f2f5717088f63 Mon Sep 17 00:00:00 2001
From: Yorick Peterse <yorickpeterse@gmail.com>
Date: Wed, 17 May 2017 22:56:23 +0200
Subject: Check if OLD is set when migrating issue assignees

The procedure for migrating issue assignees is invoked on both an INSERT
and UPDATE. This means it will fail for INSERTs because OLD is set to
NULL in this case.
---
 db/migrate/20170516153305_migrate_assignee_to_separate_table.rb | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/db/migrate/20170516153305_migrate_assignee_to_separate_table.rb b/db/migrate/20170516153305_migrate_assignee_to_separate_table.rb
index f269ca7fc34..eed9f00d8b2 100644
--- a/db/migrate/20170516153305_migrate_assignee_to_separate_table.rb
+++ b/db/migrate/20170516153305_migrate_assignee_to_separate_table.rb
@@ -47,7 +47,7 @@ class MigrateAssigneeToSeparateTable < ActiveRecord::Migration
             RETURNS trigger AS
             $BODY$
             BEGIN
-              if OLD.assignee_id IS NOT NULL THEN
+              if OLD IS NOT NULL AND OLD.assignee_id IS NOT NULL THEN
                   DELETE FROM issue_assignees WHERE issue_id = OLD.id;
               END IF;
 
-- 
cgit v1.2.1