From: | Magnus Hagander <magnus(at)hagander(dot)net> |
---|---|
To: | Dave Page <dpage(at)postgresql(dot)org> |
Cc: | Tony Caduto <tony_caduto(at)amsoftwaredesign(dot)com>, 'PostgreSQL' <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Re: pgAdmin III and pgpass was I "might" have found a bug on 8.2.1 win32 |
Date: | 2007-02-02 18:32:10 |
Message-ID: | 45C383AA.3040302@hagander.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
> I do not intend to rewrite this code (which has been in pgAdmin for
> years) on the basis of a single complaint from the author of an
> equivalent, but commercial tool. If you do not like the effects you see
> when a user has a pgpass file, you should warn them in your own code,
> not expect us to change ours to avoid using a documented feature of libpq.
Ok, as most of the regular readers know, I don't often agree with Tony
(so open your eyes, you may never see this again!), but really Dave,
that's not a true statement. I know for a fact that I have complained
about this feature at least once (I think twice) and we had a pretty
long discussion about it. And I like to see myself as a developer on the
project, and not a commercial tool ;-)
I have been bitten by this myself. Even after I knew it. And I know
others who have been. *I* think that pgAdmin *should* store the password
along with the rest of the connection options, or at least make it an
option to do so instead.
But there was a discussion, and I was in minority, so I bowed to the
majority vote. And I still do. Doesn't mean I think it's right ;-) But
I'm not going to go and commit a change for it.
//Magnus
From | Date | Subject | |
---|---|---|---|
Next Message | Magnus Hagander | 2007-02-02 18:33:00 | Re: Predicted lifespan of different PostgreSQL branches |
Previous Message | Ron Johnson | 2007-02-02 18:27:02 | Re: Problem with Online-Backup |