Scheduling infrastructure for absolutely everyone.
fix: delete team bug when instant meeting token exist (#23553)
Udit Takkar31940b919ec0
diff --git a/packages/prisma/migrations/20250903165210_add_on_cascade/migration.sql b/packages/prisma/migrations/20250903165210_add_on_cascade/migration.sqlnew file mode 100644index 00000000000..7d598800578--- /dev/null+++ b/packages/prisma/migrations/20250903165210_add_on_cascade/migration.sql@@ -0,0 +1,5 @@+-- DropForeignKey+ALTER TABLE "InstantMeetingToken" DROP CONSTRAINT "InstantMeetingToken_teamId_fkey";++-- AddForeignKey+ALTER TABLE "InstantMeetingToken" ADD CONSTRAINT "InstantMeetingToken_teamId_fkey" FOREIGN KEY ("teamId") REFERENCES "Team"("id") ON DELETE CASCADE ON UPDATE CASCADE;diff --git a/packages/prisma/schema.prisma b/packages/prisma/schema.prismaindex 867264dda2f..7d2841c744d 100644--- a/packages/prisma/schema.prisma+++ b/packages/prisma/schema.prisma@@ -702,7 +702,7 @@ model InstantMeetingToken {token String @uniqueexpires DateTimeteamId Int- team Team @relation(fields: [teamId], references: [id])+ team Team @relation(fields: [teamId], references: [id], onDelete: Cascade)bookingId Int? @uniquebooking Booking? @relation(fields: [bookingId], references: [id], onDelete: Cascade)