Circular reference issue when running migration about acts_as_relation HOT 3 CLOSED

You might be able to avoid the error you're seeing by creating dummy local models within the migration, matching the old and new model names.

class CreateTaggedObjects << ActiveRecord::Migration

  class TaggedObject << ActiveRecord::Base; end
  class TaggedObjectChild << ActiveRecord::Base; end

  def change
    create_table :tagged_objects do |t|
      # usual stuff here
    end
  end

end

It's worth mentioning that this is an order-of-operations issue: you are creating models for tables which don't exist yet. This is not isolated to the acts_as_relation gem, and can creep up with other complex Rails configurations. Even renaming a table can cause the same problem.

Even if the structure is still in flux, you should at least generate a migration that creates the table. You just need a placeholder, Rails shouldn't complain after that.

To avoid that landmine when I am laying out my models, I generally follow a 2-step dance:

1. Run rails g model to give me a model and accompanying migration
2. Run rails g migration to make any modifications to the table created in Step 1.

This only works if your Rails generator configuration is set up to create migrations along with models, so double check for setting changes to config.generators in config/application.rb.

from acts_as_relation.

Thanks to @BattleBrisket

from acts_as_relation.

Happy to help @hzamani !

from acts_as_relation.