From 0c88dcc53529bb0f4c1a3a940a237c6ac22d47ae Mon Sep 17 00:00:00 2001
From: dmitriylaukhin <laukhin@dementiy.com>
Date: Tue, 7 Apr 2026 10:46:43 +0500
Subject: [PATCH] Fix Prisma 7 client instantiation

In Prisma 7, connection URL is managed via prisma.config.ts.
PrismaClient constructor no longer accepts log options directly.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
---
 src/lib/prisma.ts | 7 ++-----
 1 file changed, 2 insertions(+), 5 deletions(-)

diff --git a/src/lib/prisma.ts b/src/lib/prisma.ts
index fbfc172..67c226b 100644
--- a/src/lib/prisma.ts
+++ b/src/lib/prisma.ts
@@ -4,10 +4,7 @@ const globalForPrisma = globalThis as unknown as {
   prisma: PrismaClient | undefined;
 };
 
-export const prisma =
-  globalForPrisma.prisma ??
-  new PrismaClient({
-    log: process.env.NODE_ENV === "development" ? ["error", "warn"] : ["error"],
-  });
+// In Prisma 7, connection is configured via prisma.config.ts, not in constructor
+export const prisma = globalForPrisma.prisma ?? new PrismaClient();
 
 if (process.env.NODE_ENV !== "production") globalForPrisma.prisma = prisma;