Peter Eisentraut wrote:
> On 11/27/12 4:20 PM, Magnus Hagander wrote:
> > On Tue, Nov 27, 2012 at 10:13 PM, Peter Eisentraut <peter_e@gmx.net> wrote:
> >> On 11/22/12 6:44 AM, Magnus Hagander wrote:
> >>> I'm thinking it might be a better idea to just have PG_CONNINFO_NORMAL
> >>> and PG_CONNINFO_PASSWORD (which still make sense to separate),
> >>
> >> What is the use case for separating them?
> >
> > Getting a connection string that doesn't contain sensitive information
> > like a password. In order to show it in a dialog box, for example.
>
> There is already the PQconninfoOption.dispchar field for this purpose.
I had the impression that that field would go away with this patch, but
then again it might not be worth the compatibility break. I find the
dispchar thingy somewhat unsightly.
--
Álvaro Herrera http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
