Help with queryRawUnsafe
Prisma Schema not updating / working
Runtime Error on latest versions of Next, AuthJS, and Prisma when initializing prisma adapter
Hi Prisma Team 👋We're currently using a Prisma Accelerate database and ran into a critical issue.
Mysql Migration for prod via docker and github action (CI/CD)
...

How can I perform batch updates unique entities in Prisma?
Promise.all([ tx.model.update(…)*N ])
for each item
2. Writing a custom extension or helper with an SQL builder
3. Executing raw SQL via tx.$executeRaw
...Prisma generate with Turborepo never prompting for name
transferring project to another workspace
Prisma with nuxt build blocking issues

ReferenceError: __dirname is not defined in ES module scope
Problem creating a new user to my database
Connecting from something like dbeaver
Anyone have Prisma ORM working with React Router 7? I get Internal server error
import prisma from "~/lib/prisma"
in a route I get [vite] Internal server error: exports is not defined
on ...app/generated/prisma/index-browser.js:4:23). RR 7.5.0. Prisma 6.6.0.output in schema
output = "app/generated/prisma/client"
seems to be very wrongly placed in the project structure whenever I simply run the following command of pnpm dlx prisma generate
and I have actually no clue to why it's doing this. Seems to me like this is a bit of an issue. Could someone please help me out here a little bit to furthermore understand exactly what's going on?
I was used to just simply have this structure prior to v7
```ts
generator client {...
Running into a strange issue
Extremely strange behavior
undefined
for the address_physical
within the Student object and I have no idea why. I suspect that because there are name similarities or the IDs to the mailing and physical addresses are the same causes Prisma to go haywire. The even weirder thing is that when I console.log the address_physical.address
, it is very clearly defined (although the same as mailing_address
, which is intended). I have checked my NestJS entity models and there are no issues there either....Prisma Data Platform visualize data

Is there a way to differently parse DateTime and db.Date when reading from Postgres
DateTime
and db.Date
are being parsed into a full Date in js. This causes unwanted behavior since the Day will shift for negative Timezones and hand-picking the affected fields for differenting handling is not a viable solution for me.
I'd like a generic way to apply a different parsing strategy for different Database types...Prisma & Store Procedures
Having trouble connecting Prisma to Aurora AWS
``✖ Introspecting based on datasource defined in prisma/schema.prisma
Error: P1001
Can't reach database server at
postgres:5432`...