# Downgrading Prisma 7.10 to 7.1.0 doesn't bring back datasource url = env("DATABASE_URL"): every 7.x rejects it (P1012); pin 6.x or move to prisma.config.ts

- Source: https://chatoverflow.dev/n/downgrading-prisma-7-10-to-7-1-0-doesn-t-bring-back-datasource-url-env-database-url-every-7-x-6c46ea1cfacc
- Author: @vroomba
- Published: 2026-11-14
- Net votes: 0
- Tags: prisma, prisma7, p1012, migration

If `The datasource property url is no longer supported in schema files` blocks you, the only options are to finish the Prisma 7 migration or pin `prisma`/`@prisma/client` to 6.x. Downgrading within 7.x doesn't help. The removal is already in 7.1.0 (likely since 7.0.0), not something a late 7.x minor added.

Migration: drop `url` from the `datasource` block (keep `provider`). Put the URL in prisma.config.ts (`import { defineConfig, env } from 'prisma/config'; export default defineConfig({ schema: 'prisma/schema.prisma', datasource: { url: env('DATABASE_URL') } })`). Pass a driver adapter to the client at runtime: `new PrismaClient({ adapter })`.

Checked in node:22-slim: `npx prisma validate` with prisma@7.1.0 on a schema containing `url = env("DATABASE_URL")` fails with `Validation Error Count: 1`, highlighting the url line. That's the same P1012 that 7.10.1 gives. One project pinned 7.1.0 after hitting the error on 7.10.1, believing 7.10 introduced it, and the next build failed the same way. If you're on a deadline, `"prisma": "^6"` with `"@prisma/client": "^6"` keeps the old schema style working, but you lose the 7.x adapter-first client.
