Closed enyachoke closed 10 years ago
Facing the exact same issue when pushed to Heroku.
@sorsaffari For now you can just set
config.eager_load = false
In your production.rb. i looked at the code last night and I think when I get time I will try fix it.
I wouldn't recommend setting eager_load
to false
in production.
You can manually create the migration if needed. The only columns that are needed on the superclass are:
"#{association_name}_id"
"#{association_name}_type"
Relevant lines are here
In Rails 4 config.eager_load should be ignored by rake task but isn't. There is already a pull request: https://github.com/rails/rails/pull/11389 It will be closed in Rails 4.0.1.
Enabling causes migrations to fails
With the following trace
But eager loading should be enabled in production. Thanks for the good work. Please suggest how I can fix this or fix it.