Feezing mysql gem + unitiliazed constant MysqlCompat::Mysql

I need to freeze the mysql gem inside my app, since it’s no longer
bundled with rails.

So, I installed the mysql 2.8.1 gem and got that “uninitialized constant
MysqlCompat::MysqlRes” error when I’m trying to deploy my app (occurring
on the first rake command).

Googling about it, I’ve found out that it’s a gem problem so I’d need to
symlink things directly or specify some ARCHFLAGS.

Problem is both solutions didn’t worked. Can anyone help me with this?

AFAICT the mysql gem has been and continues to be broken in some manner.

Downgrading the mysql gem to 2.7 whenever I encounter this problem has
shown
itself to be a consistent fix and I really have no idea why.

At the very least, whatever is causing this error could certainly
warrant
some better feedback than the arcane “uninitialized constant
MysqlCompat::MysqlRes”

Downgrading the mysql gem to 2.7 didn’t work either on rails 2.3.5
The solution I found was that my host machine didn’t had libmysql-ruby
installed. So I had to manually install it and then my deploy went fine.

On Dec 14, 3:13 pm, Tony A. [email protected] wrote:

[Note: parts of this message were removed to make it a legal post.]

AFAICT the mysql gem has been and continues to be broken in some manner.

The gem is a wrapper arount MySQL/Ruby bindings from tmtm:

http://rubyforge.org/projects/mysql-ruby

If there is a problem with the extension, like a broken API between
versions, please report it there.

On a new release of the extension I’ll wrap it and package in the
mysql gem, here:

http://github.com/luislavena/mysql-gem