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`...Prisma playground release date
Eslint errors
Relationship issue
Opened PR to add ESM support to `@prisma/instrumentation`
@prisma/instrumentation
package: https://github.com/prisma/prisma/pull/26918
The package currently not shipping in ESM is currently blocking us from auto-instrumenting prisma in the Sentry SDK. It fixes a long-standing issue. Lemme know what you think....'Too many clients' error when using NestJS and Jest even with a singleton Service
Could not locate Query Engine
Prisma Client could not locate the Query Engine for runtime "rhel-openssl-3.0.x".
...has no exported member error after updating to 6.6.0

Hello I keep getting an error that I'm stuck on
Handling @db.Date fields client side from different Timezones (Postgres)
DateTime @db.Date
) while others are regular DateTime fields.
When the server sends this data then javscript will create a new Date()
for both since we don't have a date only primitive there.
This causes the @db.Date
field which is stored as 2025-04-20
to be understood as a UTC 00:00 date. Therefore if I'm in New York which is -4h
the date will result in 2020-04-19T20.00.000Z
and the data will shift by one day in something like a calendar.
We COULD simply say that all dates that we receive client side we add the current timezones offset so that it will then be correctly parsed as 2020-04-20T00.00.000Z
. Then we woulc correctly have the beginning of the DB's date in the local timezone to correctly sort in the entry, BUT then we would mess up regular DateTime
dates. A "createdAT" timestamp from 14:00 local NY time will come back to the same client with a 18:00 time which is WRONG....Schema Troubleshooting
full Text Search not working with Postgres and Nextjs
...
