From 12d652bd0eb352a3feeaf283e874e563ae1f6748 Mon Sep 17 00:00:00 2001
From: Niek van der Kooy <niek@vanderkooy.info>
Date: Tue, 10 Mar 2015 18:25:23 +0100
Subject: [PATCH] We cannot entirely drop the foreign key constraint, since it
 is originally created (and dropped) in v3.2.1.

---
 database/migrations/2014_12_24_191544_changes_for_v322.php | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/database/migrations/2014_12_24_191544_changes_for_v322.php b/database/migrations/2014_12_24_191544_changes_for_v322.php
index 592892bb64..6ee2a55a2e 100644
--- a/database/migrations/2014_12_24_191544_changes_for_v322.php
+++ b/database/migrations/2014_12_24_191544_changes_for_v322.php
@@ -59,11 +59,12 @@ class ChangesForV322 extends Migration
         }
         );
 
-        // drop foreign key from budget_limits:
+        // drop unique constraint from budget_limits:
         Schema::table(
             'budget_limits', function (Blueprint $table) {
             $table->dropForeign('bid_foreign');
             $table->dropUnique('unique_bl_combi');
+            $table->foreign('budget_id', 'bid_foreign')->references('id')->on('budgets')->onDelete('cascade');
         }
         );