error with Rails 3.0.0 & Ruby 1.9.2 about acts_as_archive HOT 5 CLOSED

Can you check if the "archived_xxx" tables were generated after rake db:migrate?

Just saying cause I am having that exact problem. I'm trying to have a look at "also_migrate"...

from acts_as_archive.

It seems a matter of classes, when running rake db:migrate, the model classes which require a migration, need to be loaded at some point, so that "also_migrate" can pick them up.

I tried this using a pseudo migration, empty, except for some "require 'app/models/....rb'" at the file start. And it works.

from acts_as_archive.

I'm pretty sure the archive tables weren't created - can't verify because unfortunately I deleted the branch. Your note regarding requiring the model classes makes sense, I was wondering how it was going to pick those up, but hadn't bothered to look into the code.

from acts_as_archive.

@axs89: Not sure why the gem isn't loading for you. I've been executing specs under Ruby 1.9.2 and Rails 3. I will see if I can find something for you.

@echarp: You've identified a problem with also_migrate that seems to only be solved by setting $rails_rake_task = false, which forces rake to preload all activerecord classes. I'm not sure at this point if its best to put that code in the plugin or not. Coming up with a solution to that now.

from acts_as_archive.

@axs89: I have tested using a fresh project, Rails 3.0.3, and Ruby 1.9.2-p136 and cannot replicate your problem of acts_as_archive not being defined. Without any more information I am closing this ticket.

@echarp: In the latest version of acts_as_archive, I have added the $rails_rake_task = false flag. Let me know if any problems arise from this.

from acts_as_archive.