Skip to content


Subversion checkout URL

You can clone with
Download ZIP


Fix mysql2 to 0.2.x family #11

merged 2 commits into from

3 participants



The current mysql2 gem (0.3.x) is not compatible with rails 3.0.x, so I fixed it to 0.2.10 version. This is the last 0.2.x family version.


Whoa, what's up with latest mysql2? That seems like a pretty serious issue. /cc @brianmario


Actually there is a warning when I try to run it with the mysql2 0.3.6 (latest) is installed: "WARNING: This version of mysql2 (0.3.6) 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 <= 3.0.x"


Ah, gotcha. Hmm, instead of freezing the gem version, upgrading this project to latest rails shouldn't be much of a problem? Daniel, do you mind giving that a try? :)


Rails 3.1 pulled the mysql2 adapter in core, and since the version that used to ship with the gem in the 0.2.x releases is in the exact same autoload path as the adapter in 3.1, I had no choice but to remove it from mysql2 for the 0.3.x releases.

The two releases are exactly the same except 0.2.x has the ActiveRecord adapter, and 0.3.x doesn't (since it's in Rails 3.1). A better way of saying that is, for ActiveRecord 3.1+ you need to use mysql 0.3.x for any previous version you need to use mysql 0.2.x.

I hate that it needs to be done this way, I just couldn't think of anything better :\


Right, thanks Brian - that makes sense. I think the best path forward here is to just update the project to latest and greatest.


bump to rails 3.1... :)

@igrigorik igrigorik merged commit 3a554bd into igrigorik:master

Awesome, thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Commits on Jun 18, 2011
  1. @dkonishi

    fixing mysql2 to 0.2.x family

    dkonishi authored
  2. @dkonishi

    Bump to Rails 3.1.0.rc4

    dkonishi authored
Something went wrong with that request. Please try again.