Installing mysql2 gem on mac with RVM is real pain?

I have the sam problem. What I did is doing gem install --version '0.2.7' mysql2 Then on your Rails's GemFile. Should look like this gem 'mysql2', '0.2.7 Then try again.

Hope it help.

I have the sam problem. What I did is doing; gem install --version '0.2.7' mysql2 Then on your Rails's GemFile. Should look like this.

Gem 'mysql2', '0.2.7' Then try again. Hope it help.

1 This should also work, only just noticed this now. Although my (updated) solution using "~> 0.2" is slightly better because it frees bundler up to use other 0.2 bugfix releases if they're available. – Jason King Apr 28 at 19:10 I think you mean "~> 0.2.7".

OTOH, "~> 0.2" would allow anything less than 1.0. See pessimistic version constraint. – Jonathan Tran May 31 at 21:56 man -- I wasted 3 hours before finding this post.

They have got to get this gem cleaned up – Jonathan Jul 25 at 19:50.

Try this (but I cannot guarantee anything) Check this post about how to remove MySQL 5.5. Install MySQL 5.1 (I think I downloaded the 32bit DMG version) Follow this post to create the GEM. Hopefully it will work after this. I'll cross my fingers for you.

Augusto thanks bro but I am using RVM :-( – Mohit Jain Apr 28 at 12:49 I'm using RVM too, those instructions should work. I say should, because I installed it on my personal computer, and I'm not at work, so I can't check a few things (like exactly which version of mysql I downloaded, although I remember it was 5.1. X). Just curiosity, which part do you think doesn't work with RVM?

– Augusto Apr 28 at 12:50 K. Lemme try... – Mohit Jain Apr 28 at 12:56 @Augusto Oh no... He is using mysql. I am already using mysql2 for tons of my projects.

All the servers are running msql2 – Mohit Jain Apr 28 at 13:02 Sorry about that. I'll check tonight which if I compiled mysql2 following the same instructions, as the parameters to build both gems are quite similar. – Augusto Apr 28 at 13:07.

Your stacktrace after Step 2 told you what to do: Please install the mysql2 adapter: gem install activerecord-mysql2-adapter Update Also, upgrade your Rails to 3.0.7 - there are a number of security holes (and bugs) in 3.0.3. Update Looks like that error message from Rails is wrong, it should have read: Please use the 0.2. X releases if you plan on using it in Rails 0.2" Then re-run bundle install.

1 there is no such gem – Mohit Jain Apr 28 at 18:59 My bad, let me edit... – Jason King Apr 28 at 19:01 Already did.. :) I wasted my whole day dude.. and thats y finally moved back to 1.8.7 with rails 3.0.7 – Mohit Jain Apr 28 at 19:05 Btw, the move back to 1.8.7 probably just means that you moved back to a mysql2 version of 0.2.x. Ie. I don't think this is a 1.9.2 v.1.8.7 issue (because I can reproduce here with 1.8.7) – Jason King Apr 28 at 19:09 Working perfectly at @ruby1.8.7 and mysql 0.3.2 and rails 3.0.7.

But definetley your point is valid. But I can't mess with it as I am middle of very crucial project. But will definitely try once its over.

– Mohit Jain Apr 28 at 20:30.

The above problem occurs presently on EngineYard App Cloud with Ruby 1.9.2 and Rails 3.0.3. Using mysql 2.8.1 barfs because EY sets mysql2 adapter. Using mysql2 0.3.2 barfs.So I was seriously stumped.

Props to Richard Soutar's answer. It worked.

Rails sWARNING: This version of mysql2 (0.3.2) doesn't ship with the ActiveRecord adapter bundled anymore as it's now part of Rails 3.1 WARNING: Please use the 0.2. X releases if you plan on using it in Rails Gem 'mysql2', '0. 2.7.

I have the sam problem. What I did is doing.

Your stacktrace after Step 2 told you what to do.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.