paliad/034_deadlines_rule_code.down.sql at db1040968fde27c112c0c24ec3649737e74fcfab - paliad - Gitea: Git with a cup of tea

m/paliad

Files

m 53f7eae665 fix(t-paliad-111): renumber colliding migration 032→034 — production was down

Two migrations both named 032 collided when t-111 and t-112 merged in
parallel — 032_deadline_notes_en (t-112, already applied to the DB and
tracker bumped to v33) vs. 032_deadlines_rule_code (t-111). The Go
migration runner refuses to init the driver when two files share a
prefix, so paliad.de was 404 across all routes (container in restart
loop with `migration failed: ... duplicate migration file:
032_deadlines_rule_code.down.sql`).

Renumbering t-111's pair to 034 (033 was used by t-112's
trigger_events_de backfill).

2026-05-04 14:57:54 +02:00

2 lines

62 B

SQL

Raw Blame History

ALTER TABLE paliad.deadlines DROP COLUMN IF EXISTS rule_code;