From a483195eb1bdc6bf7173da3569c78cf393223908 Mon Sep 17 00:00:00 2001 From: William Allen Date: Fri, 23 Jan 2026 13:36:41 -0500 Subject: [PATCH] Delete invalid build2update rows before migration The updateid column did not have a foreign-key constraint, so it's possible for records to exist in the build2update table without a corresponding record in the buildupdate table. --- .../migrations/2026_01_15_143405_drop_build2update_table.php | 2 ++ 1 file changed, 2 insertions(+) diff --git a/database/migrations/2026_01_15_143405_drop_build2update_table.php b/database/migrations/2026_01_15_143405_drop_build2update_table.php index 712e890bc2..a3c8f9dabf 100644 --- a/database/migrations/2026_01_15_143405_drop_build2update_table.php +++ b/database/migrations/2026_01_15_143405_drop_build2update_table.php @@ -5,6 +5,8 @@ return new class extends Migration { public function up(): void { + DB::delete('DELETE FROM build2update WHERE NOT EXISTS (SELECT 1 FROM buildupdate WHERE build2update.updateid = buildupdate.id)'); + DB::statement('ALTER TABLE build ADD COLUMN updateid bigint'); DB::statement('ALTER TABLE build ADD FOREIGN KEY (updateid) REFERENCES buildupdate(id) ON DELETE SET NULL');