prisma cli push runs without error, but db on console.prisma.io not updating?
Has this been reported before?
I have followed instruction setup.
My schema.prisma file looks like this:
generator client {
provider = "prisma-client-js"
}
datasource db {
provider = "postgresql"
url = env("DATABASE_URL")
}
model User {
id String @id @default(uuid())
email String
}
my .env has the auto generated
DATABASE_URL="prisma+postgres://accelerate.prisma-data.net/?api_key=..."
I first executed npx prisma db push
I am not sure if this was correct but I had positive terminal output.
No changes in database dashboard.
Then I executed npx prisma migrate dev
Followed by the termianl output suggestion to run npx prisma migrate reset
Followed by one more execution of npx prisma migrate dev
My output always looks fine but still no changes in dashboard.
"You do not have any database models set up yet."
I do have my migration file in my code though.
My terminal output from the last run:
Environment variables loaded from .env
Prisma schema loaded from prisma/schema.prisma
Datasource "db": PostgreSQL database "postgres", schema "public" at "accelerate.prisma-data.net"
✔ Enter a name for the new migration: … create-user-table
Applying migration 20250403135846_create_user_table
The following migration(s) have been created and applied from new schema changes:
migrations/
└─ 20250403135846_create_user_table/
└─ migration.sql
Your database is now in sync with your schema.
✔ Generated Prisma Client (v6.5.0, engine=none) to ./node_modules/@prisma/client in 15ms4 Replies
You've gone full bot mode! Let me fetch that AI answer for you ASAP.
It appears you're experiencing an issue where your Prisma schema changes aren't reflecting in your Prisma Data Platform dashboard, despite successful CLI commands.
Based on the knowledge sources, this issue might be related to using Prisma Accelerate. When using Prisma Accelerate with the URL format
prisma+postgres://accelerate.prisma-data.net/?api_key=..., direct schema changes (DDL operations) are disabled.
This is similar to an issue described in a discussion where a user was trying to use Prisma Accelerate with PlanetScale and encountered the error "direct DDL is disabled" Prisma Accelerate Not Pushing to Database.
To resolve this issue, you need to:
1. Add a direct database connection URL to your .env file. This should be a direct connection to your PostgreSQL database, not through Accelerate.
2. Update your schema.prisma file to use this direct connection for migrations:
3. Then try running your migrations again with the direct connection.
If you're using a managed database service that doesn't allow direct schema changes (like some PlanetScale configurations), you might need to check their documentation for how to make schema changes.
Remember that Prisma Accelerate is primarily a connection pooling and caching service, but for schema changes, you typically need a direct database connection.
If this doesn't resolve your issue, you might want to check if there are any specific configuration requirements for your database provider or consider opening a new issue on the Prisma GitHub repository with more details about your setup.well, how do i get my direct url? i am using a prisma db Prisma Postgres®
Connected
🤔 Alright, thanks for letting us know that there's still some help needed. A team member will reply to you shortly.
In the meantime, please let us know any additional info, questions, or which parts of the answer may need clarification.
okay i think im just confused at how everything interacts.
i can see my database and user model locally at http://localhost:5555/
but what is the point of the prisma database dashboard that reflects none of my changes?
and when did i even setup a local postgres db???????