Ruby：删除Shop记录触发PostgreSQL外键约束冲突错误排查

问题场景 #

执行Shop.last.destroy时触发PostgreSQL外键约束错误：

PG::ForeignKeyViolation: ERROR:  update or delete on table "credit_changes" violates foreign key constraint "fk_rails_16918229d0" on table "sms_historicals" (ActiveRecord::InvalidForeignKey)

相关模型代码：

class SmsHistorical < ApplicationRecord
  belongs_to :customer
  belongs_to :credit_change, optional: true
  belongs_to :notification_setting, optional: true
end

class CreditChange < ActiveRecord::Base 
  belongs_to :credit
  belongs_to :customer
  has_one :sms_historicals
  has_one :email_historicals
end

对应迁移代码：

create_table :credit_changes, if_not_exists: true do |t|
  t.integer "credit_id"
  t.text "credit_notes"
  t.decimal "credit_amount_changed", precision: 4, scale: 2, default: 0.0
  t.datetime "date"
  t.string "transaction_type"
  t.datetime "created_at", null: false
  t.datetime "updated_at", null: false
end

class CreateSmsHistoricals < ActiveRecord::Migration[6.1]
  def change
    create_table :sms_historicals, if_not_exists: true do |t|
      t.string :phone_number
      t.text :message
      t.references :customer, null: true, foreign_key: true, on_delete: :cascade
      t.references :credit_change, null: true, foreign_key: true, on_delete: :cascade
      t.references :notification_setting, null: true, foreign_key: true, on_delete: :cascade
      t.timestamps
    end
  end
end

核心原因分析 #

1. 模型关联定义错误 #

CreditChange中has_one :sms_historicals使用了复数形式，违反has_one关联的语法规则：has_one对应单个关联记录，必须使用单数模型名（应为has_one :sms_historical）。复数定义会导致Rails无法识别正确关联关系，销毁CreditChange时不会自动处理关联的SmsHistorical记录。

2. 级联销毁链不完整 #

销毁Shop时，若Shop与Customer、Customer与CreditChange的关联未设置dependent选项，Rails不会自动级联销毁下游关联记录。即使迁移中设置了数据库层面的on_delete: :cascade，模型关联逻辑缺失可能导致销毁顺序异常，触发外键约束冲突。

3. 数据库外键约束可能未生效 #

虽然迁移代码声明了on_delete: :cascade，但存在迁移执行异常的可能，导致数据库中实际的外键约束未包含级联删除规则。此时删除CreditChange时，sms_historicals表中关联记录的外键仍指向已删除的credit_changes记录，触发冲突。

验证与解决步骤 #

步骤1：修正模型关联语法 #

修改CreditChange模型的has_one关联为单数形式：

class CreditChange < ActiveRecord::Base 
  belongs_to :credit
  belongs_to :customer
  has_one :sms_historical  # 修正为单数
  has_one :email_historical  # 同理修正
end

步骤2：完善级联销毁配置 #

确保上级关联设置dependent选项，保证销毁链完整：

• 在Customer模型中：

class Customer < ApplicationRecord
  belongs_to :shop
  has_many :credit_changes, dependent: :destroy
end

• 在Shop模型中：

class Shop < ApplicationRecord
  has_many :customers, dependent: :destroy
end

步骤3：验证并修复数据库外键约束 #

执行SQL查询确认外键约束的实际定义：

SELECT pg_get_constraintdef(oid) FROM pg_constraint WHERE conname = 'fk_rails_16918229d0';

若返回结果不含ON DELETE CASCADE，生成迁移修正约束：

class AddOnDeleteCascadeToSmsHistoricalsCreditChange < ActiveRecord::Migration[6.1]
  def change
    remove_foreign_key :sms_historicals, :credit_changes
    add_foreign_key :sms_historicals, :credit_changes, on_delete: :cascade
  end
end

执行迁移使配置生效：

rails db:migrate

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