Frederick Cheung wrote: > On Dec 4, 9:41�pm, Jason Smith <[EMAIL PROTECTED]> > wrote: >> > Craig >> >> Well I am running mysql x64, unfortunately there isn't a proper 64 bit >> gem(I've searched). �What I don't understand though is how it was >> running fine with just an error message(not an error but the deprecation >> warning) under 2.1.2 and now won't function at all. �So I'm hoping to > > 2.1.2 and earlier bundled a pure ruby mysql driver which would be > loaded if the native one couldn't be (usually this would be because > the native one wasn't there, but any sort of load error would trigger > the fallback), but 2.2 no longer bundles it. > >> find some workaround so that I can continue using the 64 bit Mysql(for >> perfomance). �Otherwise I guess I can just roll back from 2.2.2 but >> would like to avoid this as I like what 2.2.2 brings to the table and as >> I'm learning ruby and playing with rails don't want to be able to update >> to the latest code base's. >> > it shouldn't be an issue running a 32bit client against a 64bit > server. > > http://support.microsoft.com/kb/325680 and > http://support.microsoft.com/kb/812486 > implies this error can be triggered by having folders with 'bad' names > > Fred
I did look at both of these links earlier in my search to fix this problem, one or both of these links....can't quite remember. Anyways I think it may relate to this problem, but the problem only happens while running Rails and its currently looking for the mysql driver(?) possibly. As the Mysqlx64 service is up and running just fine in Vista and I currently have no database issues except when Rails/Ruby.exe complains about mysql when the script/console and servers are running. So is there a way I can force 2.2.2 to load some fallback mysql driver, this way I can keep using the 64 bit version of mysql and 2.2.2 rails? Guess thats what I have to figure out. I'm not sure what drop in performance I may see using Mysql x32 versus x64 but guess that may have to be considered as well, if I want to continue using 2.2.2 and can't find a workaround. thanks, Jason p.s. nice find on those links, gotta love google(least thats what I used!) -- Posted via http://www.ruby-forum.com/. --~--~---------~--~----~------------~-------~--~----~ 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@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---
