EF Core 6中EntityA与EntityB多对多关系配置及跟踪问题求助

你第一种配置中使用HasPrincipalKey会让EF Core将(CompanyId, IndividualId, InsuranceNumber, InsuranceCompanyId)视为EntityA的备用唯一键，导致EF在跟踪实体时默认认为该组合必须唯一，这与你需要允许同组合但不同Guid的EntityA实例的需求冲突。

由于EntityB的主键包含额外的SomeOtherProp字段，且你需要保留EntityA的Guid作为唯一标识，自定义连接表是最可靠的方案——既能正确建立关联，又不会干扰EF对EntityA的跟踪逻辑。

步骤1：创建连接表实体 #

public class EntityAEntityBLink
{
    // 关联EntityA的主键
    public Guid EntityAGuid { get; set; }
    // 关联EntityB的完整组合主键
    public int CompanyId { get; set; }
    public int IndividualId { get; set; }
    public string ParentInsuranceNumber { get; set; }
    public int InsuranceCompanyId { get; set; }
    public int SomeOtherProp { get; set; }

    // 导航属性
    public EntityA EntityA { get; set; }
    public EntityB EntityB { get; set; }
}

步骤2：修改实体类的导航属性 #

更新EntityA和EntityB的导航属性，指向连接表：

public class EntityA
{
    public Guid Guid { get; set; }
    public int CompanyId { get; set; }
    public int IndividualId { get; set; }
    public string InsuranceNumber { get; set; }
    public int InsuranceCompanyId { get; set; }
    // 替换为连接表的导航属性
    public ICollection<EntityAEntityBLink> EntityBLinks { get; set; }
}

public class EntityB
{
    public int CompanyId { get; set; }
    public int IndividualId { get; set; }
    public string ParentInsuranceNumber { get; set; }
    public int InsuranceCompanyId { get; set; }
    public int SomeOtherProp { get; set; }
    // 可选：若不需要从EntityB反向导航到EntityA，可直接移除该属性
    public ICollection<EntityAEntityBLink> EntityALinks { get; set; }
}

步骤3：Fluent API配置 #

在OnModelCreating中配置关联关系：

// 配置连接表的复合主键
modelBuilder.Entity<EntityAEntityBLink>()
    .HasKey(link => new 
    { 
        link.EntityAGuid, 
        link.CompanyId, 
        link.IndividualId, 
        link.ParentInsuranceNumber, 
        link.InsuranceCompanyId, 
        link.SomeOtherProp 
    });

// 配置EntityA与连接表的一对多关系
modelBuilder.Entity<EntityA>()
    .HasMany(a => a.EntityBLinks)
    .WithOne(link => link.EntityA)
    .HasForeignKey(link => link.EntityAGuid)
    .OnDelete(DeleteBehavior.Cascade); // 根据业务需求调整删除行为

// 显式指定EntityB的复合主键
modelBuilder.Entity<EntityB>()
    .HasKey(b => new 
    { 
        b.CompanyId, 
        b.IndividualId, 
        b.ParentInsuranceNumber, 
        b.InsuranceCompanyId, 
        b.SomeOtherProp 
    });

// 配置EntityB与连接表的一对多关系（因EntityB只读，设为Restrict避免误删）
modelBuilder.Entity<EntityB>()
    .HasMany(b => b.EntityALinks)
    .WithOne(link => link.EntityB)
    .HasForeignKey(link => new 
    { 
        link.CompanyId, 
        link.IndividualId, 
        link.ParentInsuranceNumber, 
        link.InsuranceCompanyId, 
        link.SomeOtherProp 
    })
    .OnDelete(DeleteBehavior.Restrict);

步骤4：查询与添加实体 #

• 查询EntityA并关联EntityB：

  var entityA = dbContext.EntityA
      .Include(a => a.EntityBLinks)
      .ThenInclude(link => link.EntityB)
      .FirstOrDefault(a => a.Guid == targetGuid);
  

• 添加新的EntityA实例（即使组合字段重复，只要Guid唯一即可）：

  var newEntityA = new EntityA
  {
      Guid = Guid.NewGuid(),
      CompanyId = existingCompanyId,
      IndividualId = existingIndividualId,
      InsuranceNumber = existingInsuranceNumber,
      InsuranceCompanyId = existingInsuranceCompanyId,
      EntityBLinks = new List<EntityAEntityBLink>
      {
          new EntityAEntityBLink
          {
              // 关联已存在的EntityB主键字段
              CompanyId = existingCompanyId,
              IndividualId = existingIndividualId,
              ParentInsuranceNumber = existingInsuranceNumber,
              InsuranceCompanyId = existingInsuranceCompanyId,
              SomeOtherProp = existingSomeOtherProp
          }
      }
  };
  
  dbContext.EntityA.Add(newEntityA);
  dbContext.SaveChanges(); // 不会再出现跟踪异常
  

自动生成的连接表会默认使用实体主键建立关联，但你需要的是基于(CompanyId, IndividualId, InsuranceNumber, InsuranceCompanyId)的关联，而非EntityA的Guid和EntityB的完整复合主键，因此自动生成的连接表无法满足你的关联逻辑，必须自定义连接表来指定关联字段。

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