Scheduling infrastructure for absolutely everyone.
fix: updatedAt routing form response migration (#20660)
Morgan2ab34004a2ce
diff --git a/packages/prisma/migrations/20250409135411_updated_at_routing_form_response/migration.sql b/packages/prisma/migrations/20250409135411_updated_at_routing_form_response/migration.sqlindex 03f6782083a..9421727a293 100644--- a/packages/prisma/migrations/20250409135411_updated_at_routing_form_response/migration.sql+++ b/packages/prisma/migrations/20250409135411_updated_at_routing_form_response/migration.sql@@ -5,4 +5,4 @@*/-- AlterTable-ALTER TABLE "App_RoutingForms_FormResponse" ADD COLUMN "updatedAt" TIMESTAMP(3) NOT NULL;+ALTER TABLE "App_RoutingForms_FormResponse" ADD COLUMN "updatedAt" TIMESTAMP(3);diff --git a/packages/prisma/schema.prisma b/packages/prisma/schema.prismaindex 17c309acc1a..cb4dffa22ce 100644--- a/packages/prisma/schema.prisma+++ b/packages/prisma/schema.prisma@@ -1067,7 +1067,7 @@ model App_RoutingForms_FormResponse {formId Stringresponse JsoncreatedAt DateTime @default(now())- updatedAt DateTime @updatedAt+ updatedAt DateTime? @updatedAtroutedToBookingUid String? @unique// We should not cascade delete the booking, because we want to keep the form response even if the routedToBooking is deleted