ruby-dev summary 25741-25780

[George Ogata]

Or better yet (though I know no one is going to agree) change hashes to
use square brackets too.

[ :a => 1, :b => 2 ]

Is this really so hard to differentiate from an array?

Very, when it's empty.

But, yeah, it's unfortunate that curlies are overloaded. I don't
really find the "visual backtracking" that David talked about a
problem. but it does seem icky that there's this "exception to the
rule" in that you can't create empty procs this way. I guess empty
procs aren't that common, though.

 

[Trans]

Very, when it's empty.

True. But

[=>]

though a bit odd looking, would work fine. With 1.9 and the new
notation for symbol keys,

[:]

could work too and it looks fairly nice, to me at least.

T.

 

[Matt Mower]

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

 

[Marcelo Paniagua]

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

Thanks


----- Original Message -----
From: "Matt Mower" <[email protected]>
To: "ruby-talk ML" <[email protected]>
Sent: Friday, March 11, 2005 10:37 AM
Subject: Re: Problems connecting MySQL with Ruby

 

[Matt Mower]

Hi Marcelo,

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

 

[James Britt]

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://www.ruby-doc.org
http://www.rubyxml.com
http://catapult.rubyforge.com
http://orbjson.rubyforge.com
http://ooo4r.rubyforge.com
http://www.jamesbritt.com

 

[Matt Mower]

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

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

M