Prisma

but so far only on my local dev. on heroku i’m getting `Could not parse URL of the datasource`

Can you provide more details? <@U01UV6YGA23>

It should be possible to connect the proxy to your heroku deployment, if that’s your setup.

i have by DATABASE_URL env variable set up as the proxy, as well as the PRISMA_CLIENT_ENGINE_TYPE, as it says in the docs

i have it working on my dev. what else can i be missing for heroku?

Maybe the engine type is not set correctly at the time of generating the client? Are you generating it on heroku? Or commiting it to the repository?

If you work without the proxy locally, for example, and push that version of the client, it’s going to be different than the one you need on heroku with the proxy.

&gt; Could not parse URL of the datasource
Is your datasource named db ?

<https://www.prisma.io/docs/concepts/components/prisma-data-platform#step-4-make-sure-that-the-datasource-url-is-read-from-environment>

i’m using the same exact names and setup as my local

```datasource db {
  provider          = "postgresql"
  url               = env("DATABASE_URL")
  shadowDatabaseUrl = env("SHADOW_DATABASE_URL")
}```
this is my datasource in my schema file

The proxy implementation has a constraint where the datasource needs to be named db for it to parse correctly. This is not an issue when not using the proxy. Hence my question

right, it is named `db`, so any idea what might be wrong? i’m so confused haha

on both local dev _and_ Heroku, `DATABASE_URL` is the proxy URL

Hey <@U01UV6YGA23>, this error means that you're using data proxy engine for Prisma but the URL provided cannot be parsed. We simply pass the value to the `URL` constructor and see if it throws: <https://github.com/prisma/prisma/blob/main/packages/engine-core/src/data-proxy/DataProxyEngine.ts#L187-L199>; my hunch is that the env var is not set correctly in Heroku. In your app, can you try to log `process.env.DATABASE_URL`?

yes, on dev it works lol. so how do u think i should debug on heroku?

&gt; In your app, can you try to log `process.env.DATABASE_URL`?

i had a feeling this is the issue, and if DATABASE_URL is returning `null`, what’s the best way to fix? it’s been working until i starting using proxy

alright ill log it and push. but yes it probably is `null`

image.png

going to check the log now.. but i have that set properly

ok it seems to work now. what could have changed haha i don’t understand

maybe you had some whitespace in the value?

i dont think so, i didnt change anything at all. so weird! but im glad it works!!

ok! keep an eye on it and ping us if it happens again

and the pooling works like a charm! incredible work