Rails - Aug 2005 - Mysql-5.0 authentication protocol error

Installed MySQL 5.0.10 beta on a fresh Windows 200 build. Ruby one-click 
installer, then Rails. When I attempt to access any datatables via my Rails 
app, I get the following error:

"Client does not support authentication protocol requested by server;
consider upgrading MySQL client"

Is MySQL 5.0 currently not supported?

-- 
Best Regards,
-Larry
"Work, work, work...there is no satisfactory alternative."
--- E.Taft Benson


_______________________________________________
Rails mailing list
Rails-1W37MKcQCpIf0INCOvqR/iCwEArCW2h5@public.gmane.org
http://lists.rubyonrails.org/mailman/listinfo/rails

It might be, but you can''t say for sure. Considering that there are
still
issues with getting MySQL 4.1 passwords to work, I wouldn''t cross my
fingers.

- Aaron ''Jomdom'' Ransley
- Web: www.jomdom.net
- Mail: jomdom-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org 
________________________________________
From: rails-bounces-1W37MKcQCpIf0INCOvqR/iCwEArCW2h5@public.gmane.org
[mailto:rails-bounces-1W37MKcQCpIf0INCOvqR/iCwEArCW2h5@public.gmane.org] On
Behalf Of Larry Kelly
Sent: Friday, August 05, 2005 2:02 AM
To: Rails-1W37MKcQCpIf0INCOvqR/iCwEArCW2h5@public.gmane.org
Subject: [Rails] Mysql-5.0 authentication protocol error

Installed MySQL 5.0.10 beta on a fresh Windows 200 build.  Ruby one-click
installer, then Rails. When I attempt to access any datatables via my Rails
app, I get the following error:

"Client does not support authentication protocol requested by server;
   consider upgrading MySQL client"

Is MySQL 5.0 currently not supported?

-- 
Best Regards,
-Larry
"Work, work, work...there is no satisfactory alternative."
            --- E.Taft Benson

> Installed MySQL 5.0.10 beta on a fresh Windows 200 build.  Ruby one-click
> installer, then Rails. When I attempt to access any datatables via my Rails
> app, I get the following error:
>  
>  "Client does not support authentication protocol requested by server;
>    consider upgrading MySQL client"
>  
>  Is MySQL 5.0 currently not supported?
I don''t know exactly how 5.0 differs from 4.1 in terms of
authentication, but to get Rails to work with 4.1, you have to use the
old-style password hash.  In other words:

SET PASSWORD FOR user@host = OLD_PASSWORD(''password'');

Because most other clients support the new password hashing method,
what I end up doing is creating a separate user just for rails with an
old password, e.g. `railsappoldpw`@`localhost` or something. Then I
have another user `railsapp` that gets the newer style password and is
used for compatible clients.  This gives you the choice.

-josh whiting
tagifieds.com | tag-based community bulletin board [powered by RoR]