EF Core中多请求实体共享Contact表的关系配置错误求助

我有两个继承自RequestItem的POCO类NewMatterRequest和DatabaseUpdateRequest，尝试让它们都使用Contact类型的列表PartiesForConflict，但配置时出现如下错误：

Cannot create a relationship between 'NewMatterRequest.PartiesForConflict' and 'Contact.Request' because a relationship already exists between 'DatabaseUpdateRequest.PartiesForConflict' and 'Contact.Request'. Navigations can only participate in a single relationship. If you want to override an existing relationship call 'Ignore' on the navigation 'Contact.Request' first in 'OnModelCreating'.

现有代码如下：

[PrimaryKey(nameof(Id))]
[NotMapped]
public abstract class RequestItem
{
    [StringLength(40)]
    [DatabaseGenerated(DatabaseGeneratedOption.None)]
    public string Id { get; set; } = Guid.NewGuid().ToString();
    [StringLength(100)]
    public string Status { get; set; } = "Pending";
    [StringLength(10)]
    public string? ClientNumber { get; set; }
    [StringLength(10)]
    public string? MatterNumber { get; set; }
    [StringLength(150)]
    public string? ClientName { get; set; }
    [StringLength(150)]
    public string? MatterName {  get; set; }
}

[PrimaryKey(nameof(Id))]
public class NewMatterRequest : RequestItem
{
     [StringLength(150)]
     public string MatterDescription { get; set; } = string.Empty;

     public List<Contact> PartiesForConflict { get; set; } = new List<Contact>(); 
}

[PrimaryKey(nameof(Id))]
public class DatabaseUpdateRequest : RequestItem
{
    public bool AddContacts { get; set; } = false;

    public List<Contact> PartiesForConflict { get; set; } = new List<Contact>();
}

[PrimaryKey(nameof(Id))]
public class Contact
{
    [StringLength(40)]
    [DatabaseGenerated(DatabaseGeneratedOption.None)]
    public string Id { get; set; } = Guid.NewGuid().ToString();
    
    public string Honarary { get; set; } = string.Empty;
    [StringLength(150)]
    public string FirstName { get; set; } = string.Empty;
    [StringLength(150)]
    public string MiddleName { get; set; } = string.Empty;
    [StringLength(150)]
    public string LastName { get; set; } = string.Empty;

    //Relationship
    public RequestItem Request { get; set; }
    [StringLength(40)]
    public string RequestId { get; set;} = string.Empty;
}

protected override void OnModelCreating(ModelBuilder modelBuilder)
{
    // ....
    modelBuilder.Entity<DatabaseUpdateRequest>().HasMany(c => c.PartiesForConflict).WithOne(o => (DatabaseUpdateRequest)o.Request).HasForeignKey(k => k.RequestId).HasPrincipalKey(o => o.Id);
    modelBuilder.Entity<NewMatterRequest>().HasMany(c => c.PartiesForConflict).WithOne(o => (NewMatterRequest)o.Request).HasForeignKey(k => k.RequestId).HasPrincipalKey(o => o.Id);
}

我的modelbuilder调用是否有误？找不到错误提示中建议的Ignore()调用位置，且担心这样做无法实现需求。是否有更好的处理方式？我试图避免创建NewMatterRequestContact/DatabaseUpdateRequestContact这类重复类来规避问题。我使用GUID作为Id，理论上Contact的RequestId字段存储GUID不会出现重复，希望让两个类型共享同一Contact表，恳请提供帮助和指导。

解决方案 #

你的原配置错误核心在于：EF Core不允许同一个导航属性（Contact.Request）同时参与两个不同的关系。下面提供两种贴合你需求的解决方式：

方案1：移除反向导航，配置单向关系（推荐） #

如果不需要从Contact反向定位到对应的请求子类，直接移除Contact中的Request导航属性，只保留RequestId外键字段，配置单向的一对多关系即可：

1. 修改Contact类：

[PrimaryKey(nameof(Id))]
public class Contact
{
    [StringLength(40)]
    [DatabaseGenerated(DatabaseGeneratedOption.None)]
    public string Id { get; set; } = Guid.NewGuid().ToString();
    
    public string Honarary { get; set; } = string.Empty;
    [StringLength(150)]
    public string FirstName { get; set; } = string.Empty;
    [StringLength(150)]
    public string MiddleName { get; set; } = string.Empty;
    [StringLength(150)]
    public string LastName { get; set; } = string.Empty;

    // 仅保留外键字段，移除Request导航属性
    [StringLength(40)]
    public string RequestId { get; set;} = string.Empty;
}

2. 更新OnModelCreating配置：

protected override void OnModelCreating(ModelBuilder modelBuilder)
{
    // 配置NewMatterRequest与Contact的单向一对多关系
    modelBuilder.Entity<NewMatterRequest>()
        .HasMany(c => c.PartiesForConflict)
        .WithOne() // 不指定反向导航
        .HasForeignKey(k => k.RequestId)
        .HasPrincipalKey(o => o.Id)
        .OnDelete(DeleteBehavior.Cascade); // 根据业务需求调整删除行为

    // 配置DatabaseUpdateRequest与Contact的单向一对多关系
    modelBuilder.Entity<DatabaseUpdateRequest>()
        .HasMany(c => c.PartiesForConflict)
        .WithOne()
        .HasForeignKey(k => k.RequestId)
        .HasPrincipalKey(o => o.Id)
        .OnDelete(DeleteBehavior.Cascade);
}

这种方式完全满足你共享Contact表的需求，且没有导航属性冲突问题。

方案2：保留反向导航，使用TPT继承策略 #

如果需要保留从Contact到请求类的反向导航，可以采用**表每类型（TPT）**继承策略，先移除RequestItem上的[NotMapped]特性：

1. 修改RequestItem类：

[PrimaryKey(nameof(Id))]
public abstract class RequestItem
{
    // 原有属性保持不变
}

2. 更新OnModelCreating配置：

protected override void OnModelCreating(ModelBuilder modelBuilder)
{
    // 配置TPT继承，每个子类对应独立表
    modelBuilder.Entity<RequestItem>().ToTable("RequestItems");
    modelBuilder.Entity<NewMatterRequest>().ToTable("NewMatterRequests");
    modelBuilder.Entity<DatabaseUpdateRequest>().ToTable("DatabaseUpdateRequests");

    // 配置Contact与RequestItem的一对多关系
    modelBuilder.Entity<Contact>()
        .HasOne(c => c.Request)
        .WithMany()
        .HasForeignKey(c => c.RequestId)
        .HasPrincipalKey(r => r.Id);
}

这种方式下，Contact.Request可以指向任意RequestItem子类实例，但会生成三张请求相关的表（父类表+两个子类表），而非将所有请求数据存在同一张表中。

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