From a101ff07c4be65826f87b2a06dd36b012d0647b6 Mon Sep 17 00:00:00 2001
From: Huskydog9988 <39809509+Huskydog9988@users.noreply.github.com>
Date: Wed, 14 May 2025 15:40:55 -0400
Subject: [PATCH] fix: allow notification nonce reuse per user

---
 .../migration.sql                                     | 11 +++++++++++
 prisma/models/user.prisma                             |  4 +++-
 2 files changed, 14 insertions(+), 1 deletion(-)
 create mode 100644 prisma/migrations/20250514193830_allow_notification_nonce_reuse_per_user/migration.sql

diff --git a/prisma/migrations/20250514193830_allow_notification_nonce_reuse_per_user/migration.sql b/prisma/migrations/20250514193830_allow_notification_nonce_reuse_per_user/migration.sql
new file mode 100644
index 0000000..035b237
--- /dev/null
+++ b/prisma/migrations/20250514193830_allow_notification_nonce_reuse_per_user/migration.sql
@@ -0,0 +1,11 @@
+/*
+  Warnings:
+
+  - A unique constraint covering the columns `[userId,nonce]` on the table `Notification` will be added. If there are existing duplicate values, this will fail.
+
+*/
+-- DropIndex
+DROP INDEX "Notification_nonce_key";
+
+-- CreateIndex
+CREATE UNIQUE INDEX "Notification_userId_nonce_key" ON "Notification"("userId", "nonce");
diff --git a/prisma/models/user.prisma b/prisma/models/user.prisma
index 20f1c60..0b4f272 100644
--- a/prisma/models/user.prisma
+++ b/prisma/models/user.prisma
@@ -24,7 +24,7 @@ model User {
 model Notification {
     id String @id @default(uuid())
 
-    nonce String? @unique
+    nonce String?
 
     userId String
     user   User   @relation(fields: [userId], references: [id])
@@ -35,4 +35,6 @@ model Notification {
     actions     String[]
 
     read Boolean @default(false)
+
+    @@unique([userId, nonce])
 }