Sequelize报错column region.region_id不存在，求关联配置解惑

我在使用Sequelize时遇到报错：column region.region_id does not exist，相关代码及执行信息如下：

1. Facility迁移文件 #

await queryInterface.createTable("facility", {
  id: {
    allowNull: false,
    autoIncrement: true,
    primaryKey: true,
    type: Sequelize.INTEGER,
  },
  name: {
    allowNull: false,
    type: Sequelize.STRING(256),
  },
  address: {
    allowNull: false,
    type: Sequelize.STRING(256),
  },
  region_id: {
    type: Sequelize.BIGINT,
    references: {
      model: "region",
      key: "id",
    },
  },
})

2. 错误的Facility模型关联配置 #

sequelize.define(
  "facility",
  {
    id: {
      allowNull: false,
      autoIncrement: true,
      primaryKey: true,
      type: DataTypes.INTEGER,
    },
    name: {
      allowNull: false,
      type: DataTypes.STRING(256),
    },
    address: {
      allowNull: false,
      type: DataTypes.STRING(256),
    },
    region_id: {
      type: DataTypes.BIGINT,
    }
})

// 错误的关联配置
Region.belongsTo(Facility, {
  foreignKey: "region_id",
});
Facility.hasOne(Region, {
  foreignKey: "region_id",
});

3. 执行生成的错误SQL #

Executing (default): SELECT "facility"."id", "facility"."name", "facility"."address", "facility"."region_id", "region"."id" AS "region.id", "region"."name" AS "region.name", "region"."region_id" AS "region.region_id" FROM "facility" AS "facility" LEFT OUTER JOIN "region" AS "region" ON "facility"."id" = "region"."region_id";

报错信息：column region.region_id does not exist

更换为以下关联配置后问题解决，但不清楚原理：

// 正确的关联配置
Facility.belongsTo(Region, {
  foreignKey: "region_id",
});
Region.hasOne(Facility, {
  foreignKey: "region_id",
});

错误原因解析 #

核心问题是关联方向完全搞反了，必须明确Sequelize中belongsTo和hasOne的核心逻辑：

• A.belongsTo(B)：表示A表持有指向B表主键的外键，外键字段存在于A表中。
• B.hasOne(A)：是A.belongsTo(B)的反向配对，逻辑一致——仍然是A表持有外键指向B的主键，只是从B的角度描述关联关系。

你的错误配置Region.belongsTo(Facility)会让Sequelize误认为：Region表中存在region_id字段，作为外键指向Facility的id。但实际region_id字段是在Facility表中，用于关联Region的id，这就导致Sequelize生成的SQL错误地去查询Region表的region_id字段，而这个字段根本不存在，最终触发报错。

正确配置的逻辑 #

Facility.belongsTo(Region, { foreignKey: "region_id" })明确告知Sequelize：

• Facility表的region_id是外键，关联到Region表的主键id。
• 对应的Region.hasOne(Facility, { foreignKey: "region_id" })是反向关联，确认Region可以关联到对应的Facility。此时Sequelize生成的SQL会正确使用Facility的region_id去关联Region的id，不会再去查找不存在的Region表region_id字段。

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