Re: Time to get rid of PQnoPasswordSupplied?

On 6/19/15 10:35 AM, Tom Lane wrote:
> On the other hand, you could argue that improving the string is going
> to break clients that do the right thing (even if klugily) in order
> to help clients that are doing the wrong thing (ie, failing without
> offering the opportunity to enter a password).  Ideally no client app
> would ever show this message to users and so its readability would not
> matter.

Could we return a HINT? Or is that part of the same string?

I agree that it's probably not worth breaking people that are doing the 
right thing. Perhaps this could be better documented, though I don't 
know where we'd put it (I doubt users would go looking in the libpq api 
docs to find it...)
-- 
Jim Nasby, Data Architect, Blue Treble Consulting, Austin TX
Data in Trouble? Get it in Treble! http://BlueTreble.com