EF Core中Transport与TransportSteps保存时循环依赖问题求助

我有一个Transport实体，它可包含多个TransportStep实体。最初用集合维护关联，为提升性能，给Transport添加了指向特定TransportStep的直接导航属性与关联，查询操作流畅高效。但保存包含TransportStep列表并设置特定关联（如PickUpTransportStepId）的Transport时，出现如下异常：

System.InvalidOperationException: Unable to save changes because a circular dependency was detected in the data to be saved: 'Transport [Added] <- TransportSteps Transport { 'TransportId' } TransportStep [Added] <- ArrivalTransportStep { 'ArrivalTransportStepId' } Transport [Added]

我认为这并非真正的循环依赖，两种关联应相互独立，请问如何在保留集合与一对一关联的同时解决该问题？

实体及配置代码 #

public class Transport
{
    public ICollection<TransportStep> TransportSteps { get; set; } = new List<TransportStep>();

    public Guid? PickUpTransportStepId { get; set; }

    public TransportStep? PickUpTransportStep { get; set; }

    public Guid? ArrivalTransportStepId { get; set; }

    public TransportStep? ArrivalTransportStep { get; set; }
}

public class TransportStep
{
    public Guid Id { get; set; }

    public Guid TransportId { get; set; }

    public Transport Transport { get; set; }
}

public class TransportConfiguration : IEntityTypeConfiguration<Transport>
{
    public void Configure(EntityTypeBuilder<Transport> builder)
    {
        builder.HasOne(transport => transport.PickUpTransportStep)
            .WithOne()
            .HasForeignKey<Transport>(transport => transport.PickUpTransportStepId)
            .OnDelete(DeleteBehavior.Restrict);

        builder.HasOne(transportStep => transportStep.ArrivalTransportStep)
            .WithOne()
            .HasForeignKey<Transport>(transport => transport.ArrivalTransportStepId)
            .OnDelete(DeleteBehavior.Restrict);
    }
}

public class TransportStepConfiguration : IEntityTypeConfiguration<TransportStep>
{
    public void Configure(EntityTypeBuilder<TransportStep> builder)
    {
        builder.HasOne(transportStep => transportStep.Transport)
            .WithMany(transport => transport.TransportSteps)
            .HasPrincipalKey(transport => transport.Id)
            .HasForeignKey(transportStep => transportStep.TransportId)
            .OnDelete(DeleteBehavior.ClientCascade);
    }
}

触发异常的代码 #

var transportStep1 = new TransportStep();
var transportStep2 = new TransportStep();

var transport = new Transport();
transport.ArrivalTransportStep = transportStep1;
transport.PickUpTransportStep = transportStep2;
transport.TransportSteps.Add(transportStep1);
transport.TransportSteps.Add(transportStep2);

dbContext.Transports.Add(transport);
dbContext.SaveChanges();

1. 拆分保存操作，分两步提交 #

EF Core会因为新增实体的双向关联依赖顺序问题检测到循环依赖，拆分保存可以打破这个顺序限制：

var transportStep1 = new TransportStep();
var transportStep2 = new TransportStep();

var transport = new Transport();
transport.TransportSteps.Add(transportStep1);
transport.TransportSteps.Add(transportStep2);

dbContext.Transports.Add(transport);
dbContext.SaveChanges(); // 第一步：先保存主实体与集合关联，生成双方ID

// 第二步：设置一对一关联并保存
transport.ArrivalTransportStep = transportStep1;
transport.PickUpTransportStep = transportStep2;
dbContext.SaveChanges();

2. 先保存主实体，再关联子实体 #

手动控制实体生成顺序，先获取Transport的ID，再给TransportStep赋值并建立一对一关联：

var transport = new Transport();
dbContext.Transports.Add(transport);
dbContext.SaveChanges(); // 先保存Transport，拿到生成的ID

var transportStep1 = new TransportStep { TransportId = transport.Id };
var transportStep2 = new TransportStep { TransportId = transport.Id };

transport.ArrivalTransportStep = transportStep1;
transport.PickUpTransportStep = transportStep2;
transport.TransportSteps.Add(transportStep1);
transport.TransportSteps.Add(transportStep2);

dbContext.SaveChanges();

3. 调整关联配置的依赖提示 #

当前配置中，Transport的两个一对一外键是可选类型，但EF仍会因插入顺序报错。可以在配置中明确告知EF，这些一对一关联无反向导航，同时确保TransportStep的TransportId优先被处理：
保持原有TransportConfiguration不变，重点在保存时先确保Transport的ID已生成，再关联TransportStep的一对一导航属性，本质和前两种方案逻辑一致。

问题根源 #

这不是数据库层面的循环依赖，而是EF Core的插入顺序检测问题：同时添加Transport和关联TransportStep时，EF无法确定插入顺序——Transport需要TransportStep的ID填充外键，而TransportStep又需要Transport的ID填充TransportId，因此触发循环依赖报错。

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