I know this was a while ago but the fix is to first make a change in your schema.prisma file. Add whatever changes you need. Then run the command you are running. It will then notice the changes you made on the file and generate the SQL needed to achieve that change. Hope this helps.
Prisma
prisma.io › home › getting started with prisma migrate › getting started with prisma migrate › getting started with prisma migrate
Getting started with Prisma Migrate | Prisma Documentation
migrations/ └─ 20210313140442_init/ └─ migration.sql · Note: The folder name will be different for you.
Neon
neon.com › docs › guides › prisma-migrations
Schema migrations with Prisma and Neon - Neon Docs
Generate migration: Run npx prisma migrate dev --name descriptive-name
how to generate a migration file with prisma - Stack Overflow
I tried this in the repository's prisma folder npx prisma migrate dev --name add_finance_tables but it shows this in the terminal ** Environment variables loaded from .env Prisma schema loaded from More on stackoverflow.com
npx prisma migrate dev --name init from tutorial not working
Once I get to the part in the supabase prisma tutorial where I run the command npx prisma migrate dev --name initnpx prisma migrate dev --name init the terminal gets stuck at: More on answeroverflow.com
`npx prisma migrate dev --name init` fails in starter project
Bug description I was following this instruction in the setup page: "Set up your database (schema migration) Initialize your new database by running a schema migration to create the necessary tables from the sample project. npx prisma mi... More on github.com
1
January 9, 2025Command `npx prisma migrate dev` failing with no error messages
Bug description Well, i started a project here and i was trying to set up my first table on my schema I have already used Prisma in the past and worked fine, but today, on the latest version, it... More on github.com
10
May 28, 2024Kitemetric
kitemetric.com › blogs › mastering-prisma-migrations-dev-vs-deploy
Mastering Prisma Migrations: Dev vs. Deploy | Kite Metric
Run the command with a descriptive name: npx prisma migrate dev --name add_post_model ·
Prisma
prisma.io › home › development and production › development and production › development and production › development and production
Development and production | Prisma Documentation
To apply the edited migration, run prisma migrate dev again.
Top answer 1 of 2
3
I know this was a while ago but the fix is to first make a change in your schema.prisma file. Add whatever changes you need. Then run the command you are running. It will then notice the changes you made on the file and generate the SQL needed to achieve that change. Hope this helps.
2 of 2
2
Are you trying to do an empty migration? Try using
prisma migrate dev --create-only
doc
Answer Overflow
answeroverflow.com › m › 1245268096017764413
npx prisma migrate dev --name init from tutorial not working - Prisma
May 29, 2024 - Environment variables loaded from .env Prisma schema loaded from prisma/schema.prisma Datasource "db": PostgreSQL database "postgres", schema "public" at "aws-0-us-west-1.pooler.supabase.com:6543" Any ideas what the issue is here? ... Hey @gaurav1998 Can you try using the non-pooled connection string, the one with port 5432 and check? ... No, you can. You just need a direct URL (as in not a pooled connection) for migrations.
Medium
medium.com › @fardeenmansuri0316 › prisma-for-beginners-setting-up-migrating-and-querying-data-050fc401fa0d
Prisma for Beginners: Setting Up, Migrating, and Querying Data | by Fardeen Mansoori | Medium
February 21, 2025 - model User { id Int @id @default(autoincrement()) email String @unique name String? profile Profile? age Int } Then, migrate these changes to the database so they reflect in your tables: npx prisma migrate dev --name added-age # (For production, ...
GitHub
github.com › prisma › prisma › issues › 26014
`npx prisma migrate dev --name init` fails in starter project · Issue #26014 · prisma/prisma
January 9, 2025 - in the command line, run npx prisma migrate dev --name init · This bug report was generated after receiving an error. The database should be overwritten. I did this because I was trying to add new models and stream changes on the table.
Author prisma
Prisma
prisma.io › home › dev › dev › dev
prisma migrate dev | Create & Apply Migrations | Prisma Documentation
The prisma migrate dev command creates and applies migrations during development.
GitHub
github.com › prisma › prisma › issues › 24305
Command `npx prisma migrate dev` failing with no error messages · Issue #24305 · prisma/prisma
May 28, 2024 - // Try Prisma Accelerate: https://pris.ly/cli/accelerate-init generator client { provider = "prisma-client-js" } datasource db { provider = "postgresql" url = env("DATABASE_URL") } model Account { id String @id @default(uuid()) @db.Uuid name String email String @unique password String @@map("accounts") } .env: DATABASE_URL="postgresql://root:root@localhost:5432/jwtauth?schema=public" my docker container is up and my table is created, i have already checked those · can someone please help? I don't think there is a way to reproduce this because i think the problem is with my machine · This is what i got when i run npx run migrate dev · No response · // This is your Prisma schema file, // learn more about it in the docs: https://pris.ly/d/prisma-schema // Looking for ways to speed up your queries, or scale easily with your serverless or edge functions?
Author prisma
DEV Community
dev.to › digitaldrreamer › prisma-migration-stuck-7l5
Prisma migration stuck? - DEV Community
January 7, 2026 - npx prisma migrate dev --name init Environment variables loaded from .env Prisma schema loaded from prisma\schema.prisma Datasource "db": PostgreSQL database "postgres", schema "public" at "aws-0-us-west-1.pooler.supabase.com:5432"
Medium
medium.com › @s.klop › introduction-to-prisma-migrations-and-database-management-with-prisma-part-8-15-6829a56dda70
Introduction to Prisma: Migrations and Database Management with Prisma — Part 8/13 | by Stephen Klop | Medium
January 31, 2024 - Command: npx prisma migrate dev --name your_migration_name
LogRocket
blog.logrocket.com › home › effortless database schema migration with prisma
Effortless database schema migration with Prisma - LogRocket Blog
June 4, 2024 - npx prisma migrate dev --name update-biography --create-only
GitHub
github.com › prisma › prisma › issues › 4748
Prisma `migrate dev` prompts for migration name when running after --create-only · Issue #4748 · prisma/prisma
December 21, 2020 - Then when you run prisma migrate dev --preview-feature to apply the changes (without changing the SQL), you are prompted for a migration name.
Author prisma
Medium
medium.com › @panat.siriwong › how-to-sync-prisma-migrations-between-prod-and-test-databases-after-divergence-528bd372d6f4
How to Sync Prisma Migrations Between Prod and Test Databases After Divergence | by Panat Por | Medium
August 18, 2024 - npx prisma migrate dev --name anything_you_want · Result: In prisma/migrations/, you will have two migration files: 0_init,and Anew migration file with a suffix _anything_you_want · Switch back to the Prod database connection. Run a command to apply the new migrations.
DEV Community
dev.to › whoffagents › prisma-migrations-in-production-zero-downtime-strategies-and-rollback-patterns-3nf1
Prisma Migrations in Production: Zero-Downtime Strategies and Rollback Patterns - DEV Community
April 9, 2026 - -- Now safe to make it required ALTER TABLE users ALTER COLUMN display_name SET NOT NULL; -- Old column can be dropped in a later deploy ALTER TABLE users DROP COLUMN name; # Development: create migration from schema changes npx prisma migrate dev --name add_display_name # Preview what will run in production npx prisma migrate status # Production: apply pending migrations npx prisma migrate deploy
Top answer 1 of 6
36
According to the Docs.
To get the Session connection pooler string, change the port to 5432. If your database is Postgres 14 and above, it will look like this
postgres://[db-user].[project-ref]:[db-password]@aws-0-[aws-region].pooler.supabase.com:5432/[db-name]
By default Supabase provides port at 6543, after changing the port to 5432 my problem solved.
2 of 6
6
Changing the default port to 5432 worked for me. Give it a shot!
Nile
thenile.dev › get started › schema migrations › prisma
Prisma - Nile Documentation
December 8, 2025 - mkdir -p prisma/migrations/1_add_posts npx prisma migrate diff \ --from-schema-datasource prisma/schema.prisma \ --to-schema-datamodel prisma/schema.prisma \ --script > prisma/migrations/1_add_posts/migration.sql
MakerWS
makerws.com › home › auditing database migration safety and fixing my prisma workflow
Prisma Migrate Dev Workflow Lessons from a SaaS Build
3 weeks ago - Run npx prisma migrate dev --name descriptive_migration_name.