ActiveRecord字符串主键模型的belongs_to关联迁移异常求助

Hey there, I’ve run into this exact issue before with string primary keys in ActiveRecord—let me walk you through how to resolve it.

The Root Problem #

ActiveRecord doesn’t automatically infer the foreign key type from the associated model’s primary key when generating migrations or setting up associations. Even though your Location model uses a string primary key, ActiveRecord will default to creating an integer location_id column in the menus table unless you explicitly tell it otherwise.

Step 1: Correct the Migration File #

If you haven’t run the CreateMenus migration yet, modify it to explicitly set location_id as a string. If you already ran the migration, you’ll need to create a new migration to alter the column type.

Case 1: Haven’t Run the Migration Yet

Update your CreateMenus migration to specify the string type for location_id:

class CreateMenus < ActiveRecord::Migration[5.1]
  def change
    create_table :menus do |t|
      # Explicitly set location_id as string to match Location's primary key
      t.string :location_id
      # Add your other Menu fields here (e.g., t.string :name)
      t.timestamps
    end

    # Optional: Add a foreign key constraint (works with databases that support it like PostgreSQL)
    add_foreign_key :menus, :locations, column: :location_id, primary_key: :id
  end
end

Case 2: Already Ran the Migration

Generate a new migration to change the location_id column type:

rails generate migration ChangeLocationIdToStringInMenus

Then edit the generated migration file:

class ChangeLocationIdToStringInMenus < ActiveRecord::Migration[5.1]
  def change
    # Note: If you already have data in the menus table, make sure existing integer values
    # can be safely converted to strings (or back up the data first!)
    change_column :menus, :location_id, :string
  end
end

Run the migration with:

rake db:migrate

Step 2: Clean Up the Model Associations (Optional but Recommended) #

While your existing model code will work, explicitly defining the foreign key and primary key in the association makes your intent clearer and avoids any potential ambiguity:

class Menu < ActiveRecord::Base
  belongs_to :location, foreign_key: :location_id, primary_key: :id
end

class Location < ActiveRecord::Base
  self.primary_key = :id # This is redundant since id is the default, but it's okay to keep for clarity
  has_many :menus, foreign_key: :location_id
end

Why This Works #

By explicitly setting the location_id column type to string in the migration, you ensure it matches the id column type in the locations table. The optional foreign key constraint adds database-level validation to enforce the association integrity.

内容的提问来源于stack exchange，提问作者NavidM