Tony Caduto wrote:
> Dave Page wrote:
>>
> I am sorry, but I believe the way pgAdmin III is using the pgpass file
> is TOTALLY WRONG, sorry but it just is.
Actually, no, it's using it *exactly as it's documented* - which is not
unlike any other win32 app. For example, if you use the IE ActiveX
control to display web pages in your app, it will remember passwords you
save there for reuse in Internet Explorer, the HTML Help reader or any
other apps that use the IE control.
> The way you make it sound is like pgAdmin III does not want to play nice
> with other applications, and I can do that to.
> I don't want to delete
> the pgpass file, but I will so my application gets the
> same rights as pgAdmin III.
No, what I'm saying is that pgAdmin is using a documented feature of
libpq, and allowing users to save and edit pgpass.conf/.pgpass files to
store the passwords for all their libpq apps.
What you are saying is that because you don't believe in the pgpass
design, you are going to summarily delete them - which I know for
absolute sure would *really* annoy some pgAdmin users that I know for a
fact have a whole heap of passwords stored in theirs. Doing that would
only hurt your products reputation, not mine.
> I have users who set their test servers to
> trust and why should I make them store a password when they don't need
> to? That's what I would have to do, force the user to enter some form of
> password, so it's not blank or force them to store a password even if
> the server is set for trust access.
pgAdmin doesn't force them to store any passwords at all. That's pure FUD.
> Sorry in advance if you don't like what I have to say, but sometimes you
> can be very stubborn and one way or the highway!!!
I know - and that's a policy that has served me very well in life. I
will listen to other ideas, but unless I'm thoroughly convinced they are
better I'm not going to change my mind in a hurry.
Regards, Dave