Escaped password working with psql but not Prisma Client

Bug description

Hello I have a generated password that is )u&rI5]FlgG|1)q57rpB8-4{S3~5?7G}. Obviously it needs to be properly escaped, so I’ve made to the point where I’ve escaped the password enough to be working with psql

psql postgres://user:\)u\&rI5]FlgG\|1\)q57rpB8-4{S3~5\?7G}@localhost:5432

• \)u\&rI5]FlgG\|1\)q57rpB8-4{S3~5\?7G} ✅ with psql
• \)u\&rI5]FlgG\|1\)q57rpB8-4{S3~5\?7G} ❌ with prisma
• )u&rI5]FlgG|1)q57rpB8-4{S3~5?7G} ❌ with psql and prisma

I’ve tried several escaping combinations, as well as URLEncoding the password, but I’ve never got to the point where what was working with psql was also working with prisma client.

Thanks in advance for any help! 🙏

How to reproduce

Prisma version "@prisma/client": "2.16.1",

Setup a PostgreSQL docker container

  postgresql:
    image: postgres:latest
    ports:
      - 5432:5432
    environment:
      POSTGRES_USER: user
      POSTGRES_PASSWORD: )u&rI5]FlgG|1)q57rpB8-4{S3~5?7G}

schema.prisma

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

datasource db {
  provider = "postgres"
  url      = env("POSTGRES_URL")
}

.env

POSTGRES_URL="postgres://user:\)u\&rI5]FlgG\|1\)q57rpB8-4{S3~5\?7G}@localhost:5432"

Run prisma migrate reset --preview-feature

The command above fails with the following error:

$ prisma migrate reset --preview-feature
Environment variables loaded from .env
Prisma schema loaded from prisma/schema.prisma
Datasource "db": PostgreSQL database ")u\&rI5]FlgG\|1\)q57rpB8-4{S3~5\", schema "public" at "user::undefined"

Error: undefined: error: Error validating: This line is not a valid definition within a datasource.
  -->  schema.prisma:4
   |
 3 |                 provider = "postgresql"
 4 |                 url = "postgres://user:\)u\&rI5]FlgG\|1\)q57rpB8-4{S3~5\?7G}@localhost:5432"
 5 |             }
   |

Expected behavior

I’d expect the escaped password working with psql to work with prisma client

Prisma information

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

datasource db {
  provider = "postgres"
  url      = env("POSTGRES_URL")
}

Environment & setup

• OS: Mac OS
• Database: PostgreSQL
• Node.js version: v15.12.0
• Prisma version:

prisma               : 2.16.1
@prisma/client       : 2.16.1
Current platform     : darwin
Query Engine         : query-engine 8b74ad57aaf2cc6c155f382a18a8e3ba95aceb03 (at node_modules/@prisma/engines/query-engine-darwin)
Migration Engine     : migration-engine-cli 8b74ad57aaf2cc6c155f382a18a8e3ba95aceb03 (at node_modules/@prisma/engines/migration-engine-darwin)
Introspection Engine : introspection-core 8b74ad57aaf2cc6c155f382a18a8e3ba95aceb03 (at node_modules/@prisma/engines/introspection-engine-darwin)
Format Binary        : prisma-fmt 8b74ad57aaf2cc6c155f382a18a8e3ba95aceb03 (at node_modules/@prisma/engines/prisma-fmt-darwin)
Studio               : 0.346.0

[emyann]

@janpio Same error unfortunately with the string you shared

$ prisma migrate reset --preview-feature
Environment variables loaded from .env
Prisma schema loaded from prisma/schema.prisma
Datasource "db": PostgreSQL database ")u\&rI5]FlgG\|1\)q57rpB8-4{S3~5\", schema "public" at "user::undefined"

Error: undefined: error: Error validating: This line is not a valid definition within a datasource.
  -->  schema.prisma:4
   |
 3 |                 provider = "postgresql"
 4 |                 url = "postgres://user:\)u\&rI5]FlgG\|1\)q57rpB8-4{S3~5\?7G}@localhost:5432"
 5 |             }
   |

[pantharshit00]

@1323ED5 We can’t encode it ourselves because then we won’t be able to determine termination points of various parts of the URL that are determined by special characters like @