simonS wrote ... > An odd one....I've sen this before and it went away, and now its back > again, and may be more a Rails issue, but each time has manifested > itself it get picked up in active scaffold code, so I'm starting > here.... > > Googling arround did not bring any specific answers. > > To solve it last time I "removed" the controllers from the project > before the migration; but this is not going to work going forwards. > > Essentially I have code in production, and have developed more models, > migrations and controllers. I'm now trying to migrate those migrations > to production and I get the error trace below.... > > The models in question do have an id column, but the table as yet does > not exist in the database...so its a chicken and egg issue....does > anyone else get this ? does it have something to do with version of > schema.rb ?
What version of Rails? There's a problem with Rails 2.2 that's caused by eager loading of application classes during migrations. The problem's been fixed Rails 2.3 according to this lighthouse ticket: http://rails.lighthouseapp.com/projects/8994/tickets/802-eager-load-application-classes-can-block-migration I recently ran across the problem, though my symptoms were a bit different than yours, and, following some of the suggestions in the lighthouse ticket, fixed it by modifying my production config to change config.cache_classes = true to config.cache_classes = !(File.basename($0) == "rake" && !ARGV.grep(/db:/).empty?) --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "ActiveScaffold : Ruby on Rails plugin" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/activescaffold?hl=en -~----------~----~----~----~------~----~------~--~---
