Ruby on Rails has_many :through与STI外键约束异常问题

基于Devise的User类通过STI实现了AdminAccount子类，同时定义了AdminTask和AdminTaskAssignment关联模型。执行AdminTaskAssignment.create(admin_account_id: 1, admin_task_id: 1)时触发外键约束错误：SQLite3::ConstraintException: FOREIGN KEY constraint failed (ActiveRecord::InvalidForeignKey)，但AdminAccount.find(1)和AdminTask.find(1)均能查询到存在的记录。

问题根源 #

STI的核心逻辑是所有子类数据都存储在父表（users）中，子类本身不需要单独的数据库表。但迁移代码里错误创建了admin_accounts表，还将admin_task_assignments的外键指向这个空表，而实际AdminAccount的记录都在users表里，自然触发外键约束失败。

解决步骤 #

1. 移除多余的admin_accounts表创建代码
   删除迁移中create_table "admin_accounts"...整段代码，STI不需要为子类单独建表。

2. 修改外键关联指向users表
   将add_foreign_key "admin_task_assignments", "admin_accounts"替换为指向users表，还可以添加类型约束（确保关联的是AdminAccount类型的记录，可选但更严谨）：

   add_foreign_key "admin_task_assignments", "users", column: "admin_account_id"
   # 可选：添加类型约束，限制关联的用户必须是AdminAccount
   add_check_constraint "admin_task_assignments", <<~SQL, name: "admin_account_is_admin"
     EXISTS (SELECT 1 FROM users WHERE users.id = admin_account_id AND users.type = 'AdminAccount')
   SQL
   

3. 调整模型关联（可选，优化严谨性）
   在AdminTaskAssignment中显式指定class_name，避免Rails自动推断错误：

   class AdminTaskAssignment < ApplicationRecord
     belongs_to :admin_account, class_name: 'AdminAccount', foreign_key: 'admin_account_id'
     belongs_to :admin_task, foreign_key: 'admin_task_id'
   end
   

4. 重新执行迁移
   回滚旧迁移后重新运行：

   rails db:rollback STEP=需要回滚的迁移步数
   rails db:migrate
   

修改后的完整迁移代码示例 #

create_table "admin_task_assignments", force: :cascade do |t|
  t.integer "admin_account_id", null: false
  t.integer "admin_task_id", null: false
  t.datetime "created_at", null: false
  t.datetime "updated_at", null: false
  t.index ["admin_account_id"], name: "index_admin_task_assignments_on_admin_account_id"
  t.index ["admin_task_id"], name: "index_admin_task_assignments_on_admin_task_id"
end

create_table "admin_tasks", force: :cascade do |t|
  t.datetime "created_at", null: false
  t.datetime "updated_at", null: false
  t.integer "client_id", null: false
  t.string "name"
  t.string "task_type"
  t.index ["client_id"], name: "index_admin_tasks_on_client_id"
end

create_table "users", force: :cascade do |t|
  t.string "email", default: "", null: false
  t.string "encrypted_password", default: "", null: false
  t.string "reset_password_token"
  t.datetime "reset_password_sent_at"
  t.datetime "remember_created_at"
  t.datetime "created_at", null: false
  t.datetime "updated_at", null: false
  t.string "type"
  t.index ["email"], name: "index_users_on_email", unique: true
  t.index ["reset_password_token"], name: "index_users_on_reset_password_token", unique: true
end

add_foreign_key "admin_task_assignments", "users", column: "admin_account_id"
add_foreign_key "admin_task_assignments", "admin_tasks"
add_foreign_key "admin_tasks", "clients"
# 可选添加类型约束
add_check_constraint "admin_task_assignments", <<~SQL, name: "admin_account_is_admin"
  EXISTS (SELECT 1 FROM users WHERE users.id = admin_account_id AND users.type = 'AdminAccount')
SQL

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