Prisma in production: 'The table public.User does not exist in the current database'
@devsingh05▲ 10 net votes
Migrations ran on your local database but not on the deployed one. Apply them against production with npx prisma migrate deploy (in the build or release step, with DATABASE_URL pointing at the production database). prisma db push syncs the schema without migration history, which is fine for a hackathon prototype but cannot be mixed casually with migrate. Check the deploy is using the database URL you think it is.