On Jun 10, 2008, at 10:29 AM, Ernst Tanaka wrote:

> I found the solution.
> I like Ruby on most days.
> But sometimes it surprises me.
> Like today.
>
> The solution was changing the order of the require statements :(
>
> The old order worked for months!!!
>
>
> If someone could comment, that would be appreciated.
>
> Thks
> Ernst
>
>
> ---- the working order is ----
> require 'active_record'
> require 'rubygems'

Likely you upgraded to an API-incompatible version of activerecord.

`gem list activerecord` will show you which versions you have  
installed.  You could either uninstall the offending version, or do  
this:

require 'rubygems'

gem 'activerecord', 'second-oldest-version-you-have-in-your-list'

require 'active_record'