Enhancement Request: Allow Database Provider Configuration via Environment Variable

[Domains18]

Problem

I frequently work with two database types, namely PostgreSQL and MySQL, in my development projects. While I can conveniently set the database URL via environment variables in my .env file, I encounter a challenge when it comes to configuring the database provider in the Prisma schema file (schema.prisma). Currently, I need to manually ensure that the database provider specified in the Prisma schema matches the one provided via the environment variable, which can be error-prone and inconvenient.

Suggested solution

I propose enhancing Prisma to support configuring the database provider via an environment variable, similar to how the database URL is configured. This enhancement would streamline the development workflow, allowing users to seamlessly switch between different database types without needing to modify the Prisma schema file manually.
I honestly do not get why the database provider cannot be allowed to use .env variables

[janpio]

We supported that in the past, but then removed it as it made it impossible to use our migration tooling.

How would you expect the generated migration SQL to be handled in that case?