Re: Question about password character in ECPG's connection string

Alban Hertroys <haramrae@gmail.com>

From: Alban Hertroys <haramrae@gmail.com>

To: Adrian Klaver <adrian.klaver@aklaver.com>

Cc: "Egashira, Yusuke" <egashira.yusuke@jp.fujitsu.com>, Giuseppe Sacco <giuseppe@eppesuigoccas.homedns.org>, "pgsql-general@postgresql.org" <pgsql-general@postgresql.org>

Date: 2019-08-28T20:19:28Z

Lists: pgsql-general

> 2)  "tcp:postgresql://localhost?user=myuser&password=password" looks like
> 
> "tcp:postgresql://localhost?user=myuser&password=my&pwd"
> 
> and password is parsed on the & and you also end up with an extra parameter pwd

Perhaps it helps to URL-encode the & in the password as %26?

Alban Hertroys
--
There is always an exception to always.

Commits

Doc: describe the "options" allowed in an ECPG connection target string.
- fd198a89ba89 9.6.16 landed
- bea87c02cee7 9.4.25 landed
- 942b78af81aa 9.5.20 landed
- 9230cc706df0 10.11 landed
- 756349c87b85 13.0 landed
- 5eec908c3c2e 12.0 landed
- 232f645ae20f 11.6 landed
Cosmetic improvements for options-handling code in ECPGconnect().
- b61a5e6a1f8d 13.0 landed