From 447546a4c2f4d625106a75374f9a182ce35b8f26 Mon Sep 17 00:00:00 2001 From: Chris Parsons <438676+chrisparsons83@users.noreply.github.com> Date: Sat, 7 Mar 2026 22:45:59 -0800 Subject: [PATCH] fix: add statement-breakpoint to schedule_event enum migration (#86) ALTER TYPE ADD VALUE cannot run inside a transaction in older PostgreSQL versions. The missing breakpoint caused migration 0033 to be skipped in production, leaving the 'schedule_event' enum value absent. Co-authored-by: Claude Sonnet 4.6 --- drizzle/0033_add_schedule_event_type.sql | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/drizzle/0033_add_schedule_event_type.sql b/drizzle/0033_add_schedule_event_type.sql index 5325b58..144627b 100644 --- a/drizzle/0033_add_schedule_event_type.sql +++ b/drizzle/0033_add_schedule_event_type.sql @@ -1,5 +1,5 @@ -- Add 'schedule_event' to event_type enum for non-scoring calendar entries -- (e.g. F1/IndyCar races that are shown in the schedule but don't award points) --- PostgreSQL does not support ADD VALUE in a transaction, but it does support it directly. - +-- PostgreSQL does not support ADD VALUE in a transaction, so we use a breakpoint. +--> statement-breakpoint ALTER TYPE "event_type" ADD VALUE IF NOT EXISTS 'schedule_event';