Rails - Sep 2009 - after upgrade to Snow Leopard how to upgrade MySQL to version 5.1 ?

Finally I could solve the mess in my dev environment by reverting the
MySQL folder to its original version (before upgrade)  so I run
Leopard but no upgrade of MySQL yet  ...

present versions  (all 32-bits as I cannot start kernel 64.. )
Rails 2.3.4
Ruby 1.8.7
MySQL-5.0.67  (libmysqlclient.1.5.dylib...)

gem mysql (2.7)

if I upgrade to MySQL-5.1.38 , I believe I have to modify my client ..
I should I proceed ?

thanks for your advice

erwin

Why not just install mac ports and use the mysql-devel port ?

in all this mess, some posts also advise not to use ports....
maybe the best move is NOT to move until Apple clarify it....
 MacBook w 64-bit architecture but EFI-32 should be allowed to boot w
64 kernel... some day (no technical reason to block it.... but who
knows the reason

On 10 sep, 05:10, heimdull
<fre...-RCI/mp9mI1I6GGFevw1D/A@public.gmane.org>
wrote:
> Why not just install mac ports and use the mysql-devel port ?
found a good URL  w utility to test all that stuff.. not an Apple one

On Sep 9, 11:22 pm, Erwin <yves_duf...-ee4meeAH724@public.gmane.org>
wrote:
> Finally I could solve the mess in my dev environment by reverting the
> MySQL folder to its original version (before upgrade)  so I run
> Leopard but no upgrade of MySQL yet  ...
>
> present versions  (all 32-bits as I cannot start kernel 64.. )
Not very relevant here but just because the kernel is 32bits doesn''t
mean that apps are - nearly everything defaults to a 32bit kernel
apparently
> Rails 2.3.4
> Ruby 1.8.7
> MySQL-5.0.67  (libmysqlclient.1.5.dylib...)
>
> gem mysql (2.7)
>
> if I upgrade to MySQL-5.1.38 , I believe I have to modify my client ..
> I should I proceed ?
The key thing is whether the version of mysql you install is the same
architecture as the version of ruby you currently have.

Fred
>
> thanks for your advice
>
> erwin

On Wed, Sep 9, 2009 at 3:22 PM, Erwin
<yves_dufour-ee4meeAH724@public.gmane.org> wrote:
>
> Finally I could solve the mess in my dev environment by reverting the
> MySQL folder to its original version (before upgrade)  so I run
> Leopard but no upgrade of MySQL yet  ...
>
> present versions  (all 32-bits as I cannot start kernel 64.. )
> Rails 2.3.4
> Ruby 1.8.7
> MySQL-5.0.67  (libmysqlclient.1.5.dylib...)
>
> gem mysql (2.7)
>
> if I upgrade to MySQL-5.1.38 , I believe I have to modify my client ..
> I should I proceed ?
>
> thanks for your advice
>
> erwin
>
>
The instructions upgrading MySQL are contained in the following post:

http://weblog.rubyonrails.org/2009/8/30/upgrading-to-snow-leopard

Good luck,

-Conrad

> >
>
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Ruby on Rails: Talk" group.
To post to this group, send email to
rubyonrails-talk-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
To unsubscribe from this group, send email to
rubyonrails-talk+unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
For more options, visit this group at
http://groups.google.com/group/rubyonrails-talk?hl=en
-~----------~----~----~----~------~----~------~--~---

> Finally I could solve the mess in my dev environment by reverting the
> MySQL folder to its original version (before upgrade)  so I run
> Leopard but no upgrade of MySQL yet  ...
>
> present versions  (all 32-bits as I cannot start kernel 64.. )
Once again: you don''t have to run kernel in 64bit mode to run apps in
that mode.
32bit kernel runs 64 bit apps just fine. Ruby that comes with snow
leopard is 64bit, so just get 64bit version of MySQL and compile mysql
gem for the 64bit arch.

Regards,
Rimantas
--
http://rimantas.com/