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.

Check if OLD is set when migrating issue assignees
cb4ee4b1 · Yorick Peterse · c75f1d3d · cb4ee4b1
Unverified Commit cb4ee4b1 authored May 17, 2017 by Yorick Peterse
Hide whitespace changes
Inline Side-by-side

Showing with 1 addition and 1 deletion

20170516153305_migrate_assignee_to_separate_table.rb ...rate/20170516153305_migrate_assignee_to_separate_table.rb +1 -1

No files found.
--- 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;