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.
This commit is contained in:
Houmgaor
2026-02-28 19:26:21 +01:00
parent 5106b905de
commit 9a5a8dfb36

View File

@@ -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;