Scheduling infrastructure for absolutely everyone.
fix: Add unique constraint to team and slug for attributes (#22357)
Joe Au-Yeung3fe9327724a7
diff --git a/packages/prisma/migrations/20250709150348_attributes_unique_on_slug_team_id/migration.sql b/packages/prisma/migrations/20250709150348_attributes_unique_on_slug_team_id/migration.sqlnew file mode 100644index 00000000000..b7f497490c0--- /dev/null+++ b/packages/prisma/migrations/20250709150348_attributes_unique_on_slug_team_id/migration.sql@@ -0,0 +1,11 @@+/*+ Warnings:++ - A unique constraint covering the columns `[teamId,slug]` on the table `Attribute` will be added. If there are existing duplicate values, this will fail.++*/+-- DropIndex+DROP INDEX "Attribute_slug_key";++-- CreateIndex+CREATE UNIQUE INDEX "Attribute_teamId_slug_key" ON "Attribute"("teamId", "slug");diff --git a/packages/prisma/schema.prisma b/packages/prisma/schema.prismaindex 170e4f301e0..1e15a62f823 100644--- a/packages/prisma/schema.prisma+++ b/packages/prisma/schema.prisma@@ -1999,9 +1999,8 @@ model Attribute {type AttributeType- name String- slug String @unique-+ name String+ slug Stringenabled Boolean @default(true)usersCanEditRelation Boolean @default(false)@@ -2012,6 +2011,7 @@ model Attribute {isWeightsEnabled Boolean @default(false)isLocked Boolean @default(false)+ @@unique([teamId, slug])@@index([teamId])}