From 9a5a8dfb3626f0712110cc88bd055e4439fee540 Mon Sep 17 00:00:00 2001 From: Houmgaor Date: Sat, 28 Feb 2026 19:26:21 +0100 Subject: [PATCH] fix(migrations): add IF NOT EXISTS guard to alliance recruiting column Without this guard, migration 0004 fails on databases where the column already exists, such as during the existing-DB-without-schema-version upgrade path where 0001 baseline is auto-marked and 0002-0005 re-applied. --- server/migrations/sql/0004_alliance_recruiting.sql | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/server/migrations/sql/0004_alliance_recruiting.sql b/server/migrations/sql/0004_alliance_recruiting.sql index 47c2a40a2..500b182dd 100644 --- a/server/migrations/sql/0004_alliance_recruiting.sql +++ b/server/migrations/sql/0004_alliance_recruiting.sql @@ -1 +1 @@ -ALTER TABLE public.guild_alliances ADD COLUMN recruiting boolean NOT NULL DEFAULT true; +ALTER TABLE public.guild_alliances ADD COLUMN IF NOT EXISTS recruiting boolean NOT NULL DEFAULT true;