@voyant-travel/framework-migrations 0.1.0

package/migrations/0001_framework_baseline.sql

@@ -0,0 +1 @@
+ALTER TABLE "bookings" ADD COLUMN "custom_fields" jsonb DEFAULT '{}'::jsonb NOT NULL;

package/migrations/0002_framework_baseline.sql

@@ -0,0 +1,2 @@
+ALTER TABLE "organizations" ADD COLUMN "custom_fields" jsonb DEFAULT '{}'::jsonb NOT NULL;--> statement-breakpoint
+ALTER TABLE "people" ADD COLUMN "custom_fields" jsonb DEFAULT '{}'::jsonb NOT NULL;

package/migrations/0003_framework_baseline.sql

@@ -0,0 +1,2 @@
+ALTER TABLE "activities" ADD COLUMN "custom_fields" jsonb DEFAULT '{}'::jsonb NOT NULL;--> statement-breakpoint
+ALTER TABLE "quotes" ADD COLUMN "custom_fields" jsonb DEFAULT '{}'::jsonb NOT NULL;

package/migrations/0004_framework_baseline.sql

@@ -0,0 +1,12 @@
+-- custom-fields unification (phase 4): retire the EAV value side table.
+-- GUARDED: refuse to drop while rows remain, so a deployment that hasn't run the
+-- backfill (starters/operator/scripts/backfill-custom-fields.ts --clear) fails
+-- the migration instead of silently losing data. Empty (backfilled) → drops.
+DO $$
+BEGIN
+  IF EXISTS (SELECT 1 FROM "custom_field_values") THEN
+    RAISE EXCEPTION 'custom_field_values still has rows — run scripts/backfill-custom-fields.ts --clear (copies values to each entity''s custom_fields column and clears the table) before upgrading, or the data will be lost.';
+  END IF;
+END $$;
+--> statement-breakpoint
+DROP TABLE "custom_field_values" CASCADE;