Cannot infer type of prisma accelerate extended client
I'm trying to use prisma accelerate so that I can use the caching functionality, but i'm running into an issue where typescript cannot actually infer the type of the resulting prisma client. This is the code i'm using to instantiate the client:
```
export function createPrismaClient() {
return new PrismaClient().$extends(withAccelerate());...
Prisma connection fails :/
Today I encountered this issue, but the system has been working fine for the past few days:
0|aia-core-backend | 2025-11-03T16:31:03: prisma:error
0|aia-core-backend | 2025-11-03T16:31:03: Invalid
prisma.branch.findMany() invocation:
0|aia-core-backend | 2025-11-03T16:31:03:...Can´t generate prisma global next.js 15.5.6 (Next.js-supabase-prisma)
Hi everyone,
I am trying to start up a new app with the following stack:
Next.js: 15.5.6...
Solution:
Solution
In the prisma.schema file, changed provider
from: "prisma-client"
to: "prisma-client-js"
...
Support
I need help in completing my project, i am not so experienced in using database and all, i've created the database and connected it, don't know what to do from there, please help
Shadow database errors
I am receving consistent P1001 erros with failed to apply cleanly to the shadow database when trying to run prisma migrate with my postgreSQL database. I have ruled out connection issues and prisma db pull runs without issue. I have tried to manually resynchronize Prisma's migration history which has worked in the past, but I am still getting the P1001 errors. Any ideas or suggestions would be greatly appriciated. thank you
Environment variables loaded from .env │
│ Prisma schema loaded from prisma\schema.prisma │
│ Datasource "db": PostgreSQL database "postgres", schema "public" at " │ ...
│ Prisma schema loaded from prisma\schema.prisma │
│ Datasource "db": PostgreSQL database "postgres", schema "public" at " │ ...
Prisma deployment with NestJS and MySQL. Difficult company policies
I'm struggling with deployment here at work. I've got a NEST app that uses mysql and we're trying to implement prisma and I'm running into config issues and can't figure out a solution
- I can't download the binaries using my DOCKERFILE. The Azure instance that it runs on to build my app doesn't have access to binaries.prisma.sh
- my root filesystem MUST be readonly once the pod is up and running. I'm. noticing that prisma migrate deploy tries to write to node_modules directory and that fails because it is read only
...
open discussion: RBAC structure for multi-tenant app
hi, im a junior dev working on a multi tenant app. this isnt a help request, just trying to clear some confusion in my head.
i got:
- user entity
- business entity
- store entity...
Prisma db push in offline setting
Hi,
For my application use case, it's hosted on an environment with no internet connection. When I run
npx prisma db push --schema <path> I get an error about trying to reach some host to download the binaries. Is it possible to skip this step? As the app is an image that had npm install ran on it so the prisma files are in the node modules...Prisma Rust free configs with pgBouncer
previously there was a work around when using pgBouncer on the rust engine to handle migrations is to define a directUrl on the schema.prisma file how would I do that when using the pg adapter on the rust-free version ?
Multiple data sources
So I get my
db which is a PrismaClient with this piece of code. We also have 2 databases which is up all the time and synced. Are there any way to use multiple database urls so if one fails it will go to the next one?
```ts
export const db =
globalForPrisma.prisma ??
new PrismaClient({...Query Engine rhel-openssl-3.0.x could not locate error
i am using next js 16.0.0 and prisma version 6.18 and i ma facing this error in production while deploying in vercel. but it works fine locally. what is the issue?
`generator client {
provider = "prisma-client"
output = "../src/generated/prisma"...
Prisma Accelerate Seems to be Down
Others is the #chat are reporting similar problems. For our application, we are having trouble creating and accessing any deployments in the preview / production environment due to the Accelerate issue.
{"code":"P6008","message":"Accelerate was not able to connect to your database. The underlying error is: error code: 522"}}...
Getting "Failed to parse syntax of config file" error following CONTRIBUTING.md setup
Hi everyone!
I'm working on my first contribution to Prisma and following the setup instructions in
CONTRIBUTING.md. I've successfully set up my sandbox environment (sandbox/my-repro), but I'm running into a validation error with the config file.
Issue:...Missing required environment variable: DATABASE_URL in GitHub CI for generate
Locally, I can build my docker image fine. But in the GitHub CI pipeline, I run into the error in the title.
However, this is a DOCKER image, I don't want to hard-code the DATABASE_URL.
```TS...
Prisma through associations
If I have a model like so
model CustomerAddresses {
customerId Int @map("customer_id")
addressId Int @unique() @map("address_id")...
Using the new generated folder question
Is the generated/prisma/internal folder supossed to be added to git ignore?
Problems with 6.18.0 in Next.js 16
Hi everyone, since I updated Prisma to version 6.18.0 in my Next.js 16 project, I’ve been having issues with the installation...
I always run the same commands, but each time I get different errors:
npm install prisma @prisma/client
npx prisma init...
Migration adds creation of foreign key that already exists
On a MySql database there is a Download table that has this definition of a foreign key (removed columns for reading purposes):
```sql
create table Download
(...
You don't have any datasource defined in your schema.prisma.
I'm trying to migrate to the new prisma.config.ts as outlined in the latest announcement. I'm running into this error.
```
╰─ npx prisma generate
Loaded Prisma config from prisma.config.ts....