I’m working on a project using Prisma with Supabase, and I encountered an issue while trying to generate a migration.
-
Supabase setup: I have my Supabase server running properly.
-
Prisma: I’m using Prisma to manage my database schema and migrations.
Command used:
npx prisma migrate dev --name <migration_name>
When I run the migration command, the following message appears, but there are no further details or errors. The migration seems to be processed, but at the end, no tables are created in my Supabase database.
Environment variables loaded from .env
Prisma schema loaded from prismaschema.prisma
Datasource "db": PostgreSQL database "postgres", schema "public" at "aws-0-ap-south-1.pooler.supabase.com:6543"
Steps Taken:
- Verified that my Supabase server is running.
- Ensured that the connection string in prisma.schema points to the correct Supabase instance.
- Ran npx prisma db pull and verified that the schema was fetched correctly.
- Tried running the migration command with and without the –name parameter.
Expected Outcome:
Prisma should generate the migration, and I should see tables created in my Supabase database.
Actual Outcome:
The migration command runs, but it doesn't show any errors or create the tables.
Can you try to use the command without the –name parameter. And also after running the migration command check the prisma/migrations folder. Are there any new migration files created? Also for getting more informations you can try debugging, check this out : https://www.prisma.io/docs/orm/prisma-client/debugging-and-troubleshooting/debugging
I was able to resolve the failure prisma migration by changing my supabase url Session connection pooler string from 6543 to 5432. As reference in this documentation below.
https://supabase.com/partners/integrations/prisma
What the supabase url looks like
DATABASE_URL=”postgres://[db-user].[project-ref]:[db-password]@aws-0-[aws-region].pooler.supabase.com:5432/[db-name]”