[BUG]: When using database url to connect to postgresql (supabase), the url breaks if there unencoded entities in the password.

[ferran9908]

Report hasn't been filed before.

• I have verified that the bug I'm about to report hasn't been filed before.

What version of drizzle-orm are you using?

0.38.3

What version of drizzle-kit are you using?

0.30.1

Other packages

No response

Describe the Bug

What is the undesired behavior?
Connection to supabase fails after replacing password in the connection url.

For example if the password contains “#”, it has to be converted to “%23”.

What is the desired result?
The desired result is that the encoding happens automatically under the hood.

[eyalkutz]

I just tried this with postgres://user:a#@localhost:5432/postgres as the url and drizzle gives the following error:

 ⨯ [TypeError: Invalid URL] {
  code: 'ERR_INVALID_URL',
  input: 'postgres://user:a#@localhost:5432/postgres',
  base: 'postgres://base',
  digest: '1004449815'
}

however the browser encodeURI() function seems to think there is nothing wrong with it although the URL constructor does error:

const uri = 'postgres://user:a#@localhost:5432/postgres';
undefined
encodeURI(uri)
'postgres://user:a#@localhost:5432/postgres'
new URL(uri)
VM1009:1 Uncaught TypeError: Failed to construct 'URL': Invalid URL
    at <anonymous>:1:1

The only way I could find to get the browser APIs to encode this URL is:

const url=new URL('postgres://user@localhost:5432/postgres')
undefined
url.password='a#'
'a#'
url.toString()
'postgres://user:a%23@localhost:5432/postgres'