EF Core中外键约束循环/多级联路径问题求助

需要在Users实体间建立两种关系：

• 协调员用户和教授用户可给多个学生用户撰写多条评论
• 赞助者用户可赞助多个学生用户，学生用户也可被多个赞助者用户赞助

以下是相关实体及ApplicationDbContext代码：

Users 实体 #

public class Users : IdentityUser
{
    [Required]
    public string IdentificationCard { get; set; } = default!;

    public string FirstName { get; set; } = default!;

    public string? SecondName { get; set; } = default!;

    public string LastName { get; set; } = default!;

    public string SecondLastName { get; set; } = default!;

    public DateTime DateBirth { get; set; } = default!;

    public int Age { get; set; } = default!;

    public Gender Gender { get; set; } = default!;

    public string Photo { get; set; } = default!;

    public string? Email { get; set; } = default!;

    public States State { get; set; } = default!;

    public ContactMethods ContactMethods { get; set; } = default!;

    public string Address { get; set; } = default!;

    public Grades Grades { get; set; }

    public ICollection<Communities> Communities { get; set; } = default!;


    [InverseProperty(nameof(Sponsorships.Sponsor))]
    public ICollection<Sponsorships?>? Sponsor { get; set; } = default!;

    [InverseProperty(nameof(Sponsorships.Sponsored))]
    public ICollection<Sponsorships?>? Sponsored { get; set; } = default!;


    [InverseProperty(nameof(Comments.Publisher))]
    public ICollection<Comments?>? PublisherComments { get; set; } = default!;

    [InverseProperty(nameof(Comments.Student))]
    public ICollection<Comments?>? StudentComments { get; set; } = default!;


    public ICollection<Courses> Courses { get; set; } = default!;

    public string? RefreshToken { get; set; }

    public DateTime RefreshTokenExpiryTime { get; set; }
}

Comments 实体 #

public class Comments
{
    [Key]
    public int CommentsId { get; set; }

    public string PublisherId { get; set; } = default!;

    [ForeignKey("PublisherId")]
    [InverseProperty(nameof(Users.PublisherComments))]
    public Users Publisher { get; set; } = default!;

    public string StudentId { get; set; } = default!;

    [ForeignKey("StudentId")]
    [InverseProperty(nameof(Users.StudentComments))]
    public Users Student { get; set; } = default!;

    public string Comment { get; set; } = default!;

    public DateTime PublishDate { get; set; } = default!;

    public States State { get; set; } = default!;
}

Sponsorships 实体 #

public class Sponsorships
{
    [Key]
    public int SponsorhipId { get; set; }

    public string SponsorId { get; set; } = default!;

    [ForeignKey("SponsorId")]
    [InverseProperty(nameof(Users.Sponsor))]
    public Users Sponsor { get; set; } = default!;

    public string SponsoredId { get; set; } = default!;

    [ForeignKey("SponsoredId")]
    [InverseProperty(nameof(Users.Sponsored))]
    public Users Sponsored { get; set; } = default!;

    public States State { get; set; }
}

ApplicationDbContext 代码 #

public ApplicationDbContext(DbContextOptions<ApplicationDbContext> options)
        : base(options)
{
}

protected override void OnModelCreating(ModelBuilder builder)
{
    var cascadeFKs = builder.Model.GetEntityTypes()
                    .SelectMany(t => t.GetForeignKeys())
                    .Where(fk => !fk.IsOwnership && fk.DeleteBehavior == DeleteBehavior.Cascade);

    foreach (var fk in cascadeFKs)
        fk.DeleteBehavior = DeleteBehavior.Restrict;

    base.OnModelCreating(builder);

    builder.Entity<Comments>()
                .HasOne(e => e.Student)
                .WithMany(e => e.StudentComments)
                .OnDelete(DeleteBehavior.ClientCascade);

    builder.Entity<Users>().HasIndex(u => u.IdentificationCard).IsUnique();
}

public DbSet<Users> AppUsers { get; set; } = default!;
public DbSet<ContactMethods> ContactMethods { get; set; } = default!;
public DbSet<Programs> Programs { get; set; } = default!;
public DbSet<Communities> Communities { get; set; } = default!;
public DbSet<Courses> Courses { get; set; } = default!;
public DbSet<Classes> Classes { get; set; } = default!;
public DbSet<Attendance> Attendances { get; set; }
public DbSet<Sponsorships> Sponsorships { get; set; } = default!;
public DbSet<Comments> Comments { get; set; } = default!;
public DbSet<Logs> Logs { get; set; } = default!;

每次更新数据库时都会报错：

Introducing FOREIGN KEY constraint 'FK_Sponsorships_AspNetUsers_SponsorId' on table 'Sponsorships' may cause cycles or multiple cascade paths. Specify ON DELETE NO ACTION or ON UPDATE NO ACTION, or modify other FOREIGN KEY constraints.
Could not create constraint or index. See previous errors.

已尝试在ApplicationDbContext中禁用级联删除，但错误仍存在，需解决该问题。

错误核心原因：Sponsorships作为多对多关联表，包含两个指向Users的外键，EF Core默认的级联删除规则会触发多条级联路径冲突。你当前的批量修改逻辑因执行顺序问题被Identity框架的默认配置覆盖，且未针对Sponsorships的外键做显式配置。

具体修复步骤 #

1. 调整配置顺序：先执行Identity的默认配置，再进行自定义修改，避免默认规则覆盖你的设置。
2. 显式配置Sponsorships外键行为：针对两个外键明确设置删除行为，阻断冲突的级联路径。
3. 保留原有有效配置：如Comments的客户端级联和Users的唯一索引。

修改后的OnModelCreating代码 #

protected override void OnModelCreating(ModelBuilder builder)
{
    // 先加载Identity的默认配置
    base.OnModelCreating(builder);

    // 批量禁用所有非所有权关系的级联删除
    var cascadeFKs = builder.Model.GetEntityTypes()
                    .SelectMany(t => t.GetForeignKeys())
                    .Where(fk => !fk.IsOwnership && fk.DeleteBehavior == DeleteBehavior.Cascade);

    foreach (var fk in cascadeFKs)
        fk.DeleteBehavior = DeleteBehavior.Restrict;

    // 显式配置Sponsorships的两个外键删除行为
    builder.Entity<Sponsorships>()
        .HasOne(s => s.Sponsor)
        .WithMany(u => u.Sponsor)
        .OnDelete(DeleteBehavior.Restrict);

    builder.Entity<Sponsorships>()
        .HasOne(s => s.Sponsored)
        .WithMany(u => u.Sponsored)
        .OnDelete(DeleteBehavior.Restrict);

    // 保留Comments的客户端级联配置
    builder.Entity<Comments>()
                .HasOne(e => e.Student)
                .WithMany(e => e.StudentComments)
                .OnDelete(DeleteBehavior.ClientCascade);

    // 保留身份证号唯一索引
    builder.Entity<Users>().HasIndex(u => u.IdentificationCard).IsUnique();
}

补充说明 #

• DeleteBehavior.Restrict：阻止数据库自动级联删除，删除用户时需手动清理关联的Sponsorships记录；若希望EF Core在内存中自动处理关联实体删除，可改用DeleteBehavior.ClientRestrict。
• 若使用SQL Server，DeleteBehavior.NoAction与Restrict效果类似，区别在于约束检查的时机（NoAction在约束验证阶段，Restrict在删除触发阶段）。

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