Ruby-dev summary 25741-25780

Hello there!

  I'm using Tomita Masahiro MySQL-Ruby 2.5 Library and MySQL 4.1. When I try to connect, I receive the following message:

Client does not support authentication protocol

Any idea how to correct this? It seems the library works well when it connects via an anonymous account.

Thanks!

Marcelo Paniagua L.

···

--
Este correo esta libre de virus!

I believe that this has to do with MySQL changing its authentication protocol.

-austin

···

On Tue, 8 Mar 2005 04:34:02 +0900, Marcelo Paniagua <paniagua@pcmxl.com.mx> wrote:

Hello there!

  I'm using Tomita Masahiro MySQL-Ruby 2.5 Library and MySQL 4.1. When I
try to connect, I receive the following message:

Client does not support authentication protocol

Any idea how to correct this? It seems the library works well when it
connects via an anonymous account.

--
Austin Ziegler * halostatue@gmail.com
               * Alternate: austin@halostatue.ca

The password style has changed in MySQL 4.1. I have seen this error
message when trying to access a MySQL 4.1 server with a MySQL 4.0
client. The problem was fixed with the OLD_PASSWORD() function
mentioned here:

  http://dev.mysql.com/doc/mysql/en/old-client.html

Don

···

On Tue, 8 Mar 2005 04:34:02 +0900, Marcelo Paniagua <paniagua@pcmxl.com.mx> wrote:

Hello there!

  I'm using Tomita Masahiro MySQL-Ruby 2.5 Library and MySQL 4.1. When I
try to connect, I receive the following message:

Client does not support authentication protocol

Any idea how to correct this? It seems the library works well when it
connects via an anonymous account.

Thanks!

Marcelo Paniagua L.

--
Este correo esta libre de virus!

--
Don Owens
regexman@gmail.com

I believe that this has to do with MySQL changing its authentication protocol.

Yes, if I recall correctly, Tomita Masahiro's MySQL-Ruby 2.5 library
only works with MySQL < 4.1 (we use 4.0.20 at work just fine).

I created a patch for Tomita's client (which is included as a part of
Rails ActiveRecord) to handle the 4.1 authentication protocol. There
are, I think, a few issues still with mixed access (i.e. access a 4.1
and pre-4.1 server in the same session) but otherwise it seems robust.

The only way to obtain it at the moment is to install the activerecord
gem (or use svn).

Regards,

Matt

···

On Tue, 8 Mar 2005 05:03:06 +0900, Belorion <belorion@gmail.com> wrote:

> I believe that this has to do with MySQL changing its authentication protocol.

Yes, if I recall correctly, Tomita Masahiro's MySQL-Ruby 2.5 library
only works with MySQL < 4.1 (we use 4.0.20 at work just fine).

--
Matt Mower :: http://matt.blogs.it/

While using this unit, what would be the correct unit to require? mysql411.rb or mysql.rb?

Thanks

···

----- Original Message ----- From: "Matt Mower" <matt.mower@gmail.com>
To: "ruby-talk ML" <ruby-talk@ruby-lang.org>
Sent: Friday, March 11, 2005 10:37 AM
Subject: Re: Problems connecting MySQL with Ruby

I created a patch for Tomita's client (which is included as a part of
Rails ActiveRecord) to handle the 4.1 authentication protocol. There
are, I think, a few issues still with mixed access (i.e. access a 4.1
and pre-4.1 server in the same session) but otherwise it seems robust.

The only way to obtain it at the moment is to install the activerecord
gem (or use svn).

Regards,

Matt

--
Matt Mower :: http://matt.blogs.it/

--
Este correo esta libre de virus!

--
Este correo esta libre de virus!

Matt Mower wrote:

I created a patch for Tomita's client (which is included as a part of
Rails ActiveRecord) to handle the 4.1 authentication protocol. There
are, I think, a few issues still with mixed access (i.e. access a 4.1
and pre-4.1 server in the same session) but otherwise it seems robust.

The only way to obtain it at the moment is to install the activerecord
gem (or use svn).

Has this patch been offered to Tomita so it can be rolled into the stand-alone ruby-mysql lib?

Thanks,

James

···

--

http://catapult.rubyforge.com
http://orbjson.rubyforge.com
http://ooo4r.rubyforge.com
http://www.jamesbritt.com

Hi Marcelo,

···

On Tue, 15 Mar 2005 07:20:42 +0900, Marcelo Paniagua <paniagua@pcmxl.com.mx> wrote:

While using this unit, what would be the correct unit to require?
mysql411.rb or mysql.rb?

First mysql, then mysql411. The latter redefines a few methods from
the former to handle 4.1+ authentication and working out which route
to take.

Regards,

Matt

--
Matt Mower :: http://matt.blogs.it/

Not at this point but it certainly was my intention. I should take
another look at this.

M

···

On Apr 2, 2005 3:59 PM, James Britt <james_b@neurogami.com> wrote:

Matt Mower wrote:
>
> I created a patch for Tomita's client (which is included as a part of
> Rails ActiveRecord) to handle the 4.1 authentication protocol. There
> are, I think, a few issues still with mixed access (i.e. access a 4.1
> and pre-4.1 server in the same session) but otherwise it seems robust.
>
> The only way to obtain it at the moment is to install the activerecord
> gem (or use svn).

Has this patch been offered to Tomita so it can be rolled into the
stand-alone ruby-mysql lib?

--
Matt Mower :: http://matt.blogs.it/