(Re)Introspection does not respect variables in dotenv file when schema is located in a custom directory

Bug description

When the schema file is located in a custom directory, the dotenv file located in the same directory as the schema file, is not read by the Prisma CLI.

How to reproduce

Assuming we have the following project structure,

• test-prisma-dotenv
  • db
    • .env
    • schema.prisma
  • node_modules
  • package.json
  • yarn.lock

Then run the following command to re-introspect in the project root directory

yarn prisma introspect --schema db/schema.prisma --experimental-reintrospection

Results in such error

Introspecting based on datasource defined in db/schema.prisma …
Error: Error in datamodel: ErrorCollection { errors: [EnvironmentFunctionalEvaluationError { var_name: "DATABASE_URL", span: Span { start: 160, end: 179 } }] }

However, if we run the command without the --experimental-reintrospection, it works as expected that the Prisma CLI respects the environment variable in the dotenv file.

Expected behavior

Prisma information

// This is your Prisma schema file,
// learn more about it in the docs: https://pris.ly/d/prisma-schema

datasource db {
  provider = "postgresql"
  url      = env("DATABASE_URL")
}

generator client {
  provider = "prisma-client-js"
}

Environment & setup

• OS:
• Database:
• Prisma version:
• Node.js version:

[janpio]

Please create a new issue @mjknight50 and supply some more information - best fill the issue template.

[mjknight50]

@timsuchanek This same error happened for me today. ErrorCollection { errors: [EnvironmentFunctionalEvaluationError { var_name: "DATABASE_URL"

“@prisma/cli”: “^2.8.0”, “@prisma/client”: “^2.6.2”,

My schema is:

generator client {
  provider = "prisma-client-js"
}

datasource mysql {
  provider = "mysql"
  url      = env("DATABASE_URL")
}

The path is irregular: /server/data/prisma/schema.prisma