Note: Serious criticism follows since I want to see rails improve.
I was a happy camper getting along well with introducing myself with RoR
2.2.2 when disaster struck and I think I am not alone (a Google search
So, I am looking for definitive actions to get out of the mess. Please
don’t suggest to work with sqlite3 to begin with. I want to get mysql
and rails 2.2.2 to speak to each other now.
- Ubuntu installed – 8.0.4.
- Lamp server reinstalled, just to wipe everything clean (sudo apt-get
install lamp-server, this (hopefully) installs everything right).
- Mysqld started
- Ruby Gems installed.
- gem install rails --> fetches rails 2.2.2.
- rails --database=mysql people -> creates the standard structure
- change the database.yml to reflect mysql password.
- change the migrate file a bit to match a model created using
script/generate model Person
- rake db:migrate
This wreaks a havoc.
!!! The bundled mysql.rb driver has been removed from Rails 2.2. Please
install the mysql gem and try again: gem install mysql.
no such file to load – mysql
Somewhere I even saw a fierce reaction (like WTF?) to removing mysql.rb
from rails 2.2. This is just unfortunate.
- I press on.
- [email protected]:~/Projects/ror/people$ sudo gem install mysql
[sudo] password for kedar:
Building native extensions. This could take a while…
ERROR: Error installing mysql:
ERROR: Failed to build gem native extension.
A HUGE trace follows. I am losing patience now.
Why doesn’t rails behave?
Why can’t gem improve the situation?
Please help and sorry to vent the frustration. But where else to vent it
if not here?
Thank you in advance.