FG
💻 Software🗄️ DatabasesVercel

Prisma 7 breaking changes to Prisma config file, and prisma schema

Fresh4 months ago
Mar 14, 20260 views
Confidence Score76%
76%

Problem

When upgrading to the latest version of prisma, i am getting issues with the config file saying engine:'classic' engine doesnt exist, then on project build i am getting an error saying the url in the db source block is deprecated but when removing it i get and error saying it is required to be added. <img width="662" height="137" alt="Image" src="https://github.com/user-attachments/assets/df2e918a-c541-4f55-8cca-3a573babbfc2" /> `npx prisma generate Loaded Prisma config from prisma.config.ts. Prisma schema loaded from prisma\schema.prisma Error: Prisma schema validation - (get-config wasm) Error code: P1012 error: The datasource property `url` is no longer supported in schema files. Move connection URLs for Migrate to `prisma.config.ts` and pass either `adapter` for a direct database connection or `accelerateUrl` for Accelerate to the `PrismaClient` constructor. See https://pris.ly/d/config-datasource and https://pris.ly/d/prisma7-client-config --> prisma\schema.prisma:11 | 10 | provider = "postgresql" 11 | url = env("DATABASE_URL") | Validation Error Count: 1 [Context: getConfig] Prisma CLI Version : 7.0.0` `{ "name": "ypay", "version": "0.1.0", "private": true, "scripts": { "dev": "next dev", "build": "next build", "start": "next start", "lint": "next lint" }, "dependencies": { "@aws-sdk/client-s3": "^3.856.0", "@prisma/adapter-pg": "^7.0.0", "@prisma/client": "7.0.0", "@prisma/extension-accelerate": "^2.0.2",

Error Output

error saying the url in the db source block is deprecated but when removing it i get and error saying it is required to be added. 

Unverified for your environment

Select your OS to check compatibility.

1 Fix

Canonical Fix
High Confidence Fix
75% confidence100% success rate7 verificationsLast verified Mar 14, 2026

Solution: Prisma 7 breaking changes to Prisma config file, and prisma schema

Low Risk

Having the same issue. Ever since i upgraded from 6.19 i have officially went through the worst day of dev

75

Trust Score

7 verifications

100% success
  1. 1

    Having the same issue. Ever since i upgraded from 6.19 i have officially went th

    Having the same issue. Ever since i upgraded from 6.19 i have officially went through the worst day of dev

Validation

Resolved in prisma/prisma GitHub issue #28573. Community reactions: 39 upvotes.

Verification Summary

Worked: 7
Partial: 2
Last verified Mar 14, 2026

Sign in to verify this fix

Environment

Submitted by

AC

Alex Chen

2450 rep

Tags

prismaormpostgresql