Prisma no longer supports `url` and `directUrl` in `schema.prisma`, forcing DB connection to be defined in code and breaking Supabase migration flow

In the latest Prisma version (7.2.0), the database connection can no longer be defined inside schema.prisma using DATABASE_URL. Previously, Prisma allowed defining the database connection directly in the schema file: ```prisma datasource db { generator client { provider = "prisma-client-js" } datasource db { provider = "postgresql" url = env("DATABASE_URL") directUrl = env("DIRECT_URL") } } ``` However, this no longer works in the current version. The schema now requires the datasource to not include url and directUrl, and the database connection must instead be defined directly when instantiating PrismaClient in application code. Example of the current required setup: ``` typescript import { PrismaPg } from '@prisma/adapter-pg' import { PrismaClient } from '../generated/prisma/client' const adapter = new PrismaPg({ connectionString: process.env.DATABASE_URL }) const prisma = new PrismaClient({ adapter }) ``` Since Supabase still requires two separate database URLs, one for application runtime (pooled connection) and another for migrations (direct connection), this change creates a significant workflow issue. Currently, `prisma.config.ts` relies on `DATABASE_URL`: ```typescript datasource: { url: process.env["DATABASE_URL"], } ``` However, when running: ```bash npx prisma migrate ``` the command fails to migrate (stuck) because Supabase does not allow migrations using the pooled connection. Migrations must use the direct connection URL instead. As a result, developers are forced to manually replace `DATABASE_URL` with `DIRECT_URL` in the configuration whenever running migrations. This is error-prone, breaks automation, and defeats the purpose of having separate connection types. This behavior makes Prisma’s current workflow incompatible with Supabase’s recommended connection setup