Randy Chrismon <[EMAIL PROTECTED]> wrote:
>>>Don't think this is the issue. If it were, I wouldn't be able to use
>>> MySQLCC on my own local database which is also 4.1.0 alpha, would I?
>
>
>> Do you use password when you connect to the local 4.1 MySQL server?
>
> Yes. No password, no entry.
Don't think this is the issue. If it were, I wouldn't be able to use
MySQLCC on my own local database which is also 4.1.0 alpha, would I?
Do you use password when you connect to the local 4.1 MySQL server?
Yes. No password, no entry.
Can you connect without --protocol option using 4.1 mysql com
Randy Chrismon <[EMAIL PROTECTED]> wrote:
> Victoria Reznichenko wrote:
>
>>MySQL 4.1 provides new password hashing mechanism. This error appears if you connect
>>with pre-4.1 client to the server 4.1. ook at:
>> http://www.mysql.com/doc/en/Password_hashing.html
>>
>>In the above section of
Victoria Reznichenko wrote:
MySQL 4.1 provides new password hashing mechanism. This error appears if you connect
with pre-4.1 client to the server 4.1. ook at:
http://www.mysql.com/doc/en/Password_hashing.html
In the above section of the manual you can find description of possible scenari
"Randy Chrismon" <[EMAIL PROTECTED]> wrote:
>
> This irritating rather than life-threatening: I can connect to the
> MySQL database on my Linux box, from my Win2K box, using the command
> line environment just fine:
>
> c:>mysql --protocol=TCP -h host_name -u my_name -p mysql
>
> No matter what
This irritating rather than life-threatening: I can connect to the
MySQL database on my Linux box, from my Win2K box, using the command
line environment just fine:
c:>mysql --protocol=TCP -h host_name -u my_name -p mysql
No matter what I try, however, I can't connect using MySQLCC. I
always
get
