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

Not specified by the original author.

The problem

Issue prisma/orm#28573 (closed, 73 comments): 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. [image] 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.

What to do

[nonacc / otsairaze (commenters)]: Prisma 7 moved config out of schema.prisma into prisma.config.ts, which breaks two things. (1) Seeding fails with "Cannot read properties of undefined (__internal)" because Prisma 7 no longer auto-detects the database provider: add an explicit adapter in prisma.config.ts. (2) In Docker multi-stage builds, make sure prisma.config.ts is copied into the final image, or migrate deploy fails with "The datasource property is required in your Prisma config file".

In the GitHub issue gh:prisma/orm#28573 (https://github.com/prisma/orm/issues/28573), the problem reported was: Issue prisma/orm#28573 (closed, 73 comments): 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. [image] 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. The verified resolution was: [nonacc / otsairaze (commenters)]: Prisma 7 moved config out of schema.prisma into prisma.config.ts, which breaks two things. (1) Seeding fails with "Cannot read properties of undefined (__internal)" because Prisma 7 no longer auto-detects the database provider: add an explicit adapter in prisma.config.ts. (2) In Docker multi-stage builds, make sure prisma.config.ts is copied into the final image, or migrate deploy fails with "The datasource property is required in your Prisma config file".