The password wasn't the "solution" but another part of the puzzle.
However, I can work around the issue now using a password AND verifiy
that the database it connects to is the one the user requested. I
will consider it a failed connection unless both of those tests pass.
There is still strange behavior from RB's PostgreSQLDatabase class. I
can get the .Connect to return true even if the passwords are wrong --
but it will then report connecting to the "postgres" database. So
apparently I can only rely on .Connect to let me know that the server
host and port is correct. I need to validate the requested database
is connected (with select current_database() ) as well to ensure the
suer/pass and database names are correct.
Basically, I have a hack to work around the problem.
Robert
On Apr 30, 2008, at 11:21 AM, Norman Palardy wrote:
>
> On 30-Apr-08, at 9:45 AM, Robert Lawrence wrote:
>
>> I should have read your bug report more closely.
>>
>> It's just an incorrect status report. As I was working on a
>> development box, test PostgreSQL server, the accounts had no
>> password. Once I assigned a password, I was able to select databases
>> besides the one named the same as the username.
>>
>> However, I can verify that your bug report was 100% dead on what I am
>> experiencing. This is on an intel iMac, OS X 10.5.2, and RealBasic
>> 2008 R1.
>>
>> Regards,
>> Robert
>
> Interesting
> So in your case adding a password is the solution ?
> Seems odd that in my case pgsql can log in with no password and RB
> can't
> _______________________________________________
> Unsubscribe or switch delivery mode:
> <http://www.realsoftware.com/support/listmanager/>
>
> Search the archives:
> <http://support.realsoftware.com/listarchives/lists.html>
_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>
Search the archives:
<http://support.realsoftware.com/listarchives/lists.html>
|