基于.NET 8与EF Core 8，如何为用户生成独立的图书实体副本？

我是Entity Framework新手，个人项目需要复杂的实体数据结构，当前使用.NET 8和Entity Framework Core v8。我希望每个使用MS Identity的AppUser用户，能拥有现有Books/Chapter/Page实体的独立副本，可添加自定义数据（如标记章节或页面IsCompleted=true、添加笔记），且用户间数据互不干扰。现有数据库上下文及实体类如下，请问该如何实现？是否使用映射表？最佳方案是什么？

现有数据库上下文 #

public class AppDbContext : IdentityDbContext<AppUser, IdentityRole, string>
{
     public DbSet<Book> Books { get; set; }
     public DbSet<Chapter> Chapters { get; set; }
     public DbSet<Page> Pages { get; set; }
     
     public AppDbContext(DbContextOptions options)
        : base(options)
     {
     }
}

现有实体类 #

public class Book
{
    [Key]
    public Guid Id { get; set; } = Guid.NewGuid();

    [Required]
    public string Name { get; set; } = string.Empty;
    public string Description { get; set; } = string.Empty;
    public decimal Price { get; set; } = decimal.Zero;

    public ICollection<Chapter> Chapters { get; set; } = new List<Chapter>();
}

public class Chapter
{
    [Key]
    public Guid Id { get; set; } = Guid.NewGuid();

    [Required]
    public string Title { get; set; } = string.Empty;
    public string Description { get; set; } = string.Empty;

    public ICollection<Page>? Pages { get; set; } = new List<Page>();

    [ForeignKey("BookId")]
    public string BookId { get; set; }
    public Book Book { get; set; }
}

public class Page
{
    [Key]
    public Guid Id { get; set; } = Guid.NewGuid();

    public int Number { get; set; } = 0;
    public string Notes { get; set; } = string.Empty;

    [ForeignKey("ChapterId")]
    public string ChapterId { get; set; }
    public Chapter Chapter { get; set; }
}

最佳实现方案 #

核心结论 #

不需要使用映射表，映射表适用于多用户共享同一资源的场景（如收藏书籍）。你的需求是每个用户拥有独立副本，最直接高效的方案是为每个实体添加与AppUser的关联，并扩展自定义字段。

具体实现步骤 #

1. 修改实体类，添加用户关联与自定义字段

调整实体结构，确保每个Book属于单个用户，同时在Chapter和Page中添加自定义状态字段：

// Book类：添加用户关联
public class Book
{
    [Key]
    public Guid Id { get; set; } = Guid.NewGuid();

    [Required]
    public string Name { get; set; } = string.Empty;
    public string Description { get; set; } = string.Empty;
    public decimal Price { get; set; } = decimal.Zero;

    // 关联当前用户
    [ForeignKey(nameof(AppUser))]
    public string UserId { get; set; }
    public AppUser AppUser { get; set; }

    public ICollection<Chapter> Chapters { get; set; } = new List<Chapter>();
}

// Chapter类：添加IsCompleted自定义字段，修正外键类型与Book.Id一致
public class Chapter
{
    [Key]
    public Guid Id { get; set; } = Guid.NewGuid();

    [Required]
    public string Title { get; set; } = string.Empty;
    public string Description { get; set; } = string.Empty;

    // 自定义字段：标记章节是否完成
    public bool IsCompleted { get; set; } = false;

    public ICollection<Page>? Pages { get; set; } = new List<Page>();

    [ForeignKey("BookId")]
    public Guid BookId { get; set; } // 改为Guid，与Book.Id类型匹配
    public Book Book { get; set; }
}

// Page类：添加IsCompleted字段，拆分用户笔记字段
public class Page
{
    [Key]
    public Guid Id { get; set; } = Guid.NewGuid();

    public int Number { get; set; } = 0;
    // 用户自定义笔记
    public string UserNotes { get; set; } = string.Empty;
    // 自定义字段：标记页面是否完成
    public bool IsCompleted { get; set; } = false;

    [ForeignKey("ChapterId")]
    public Guid ChapterId { get; set; } // 改为Guid，与Chapter.Id类型匹配
    public Chapter Chapter { get; set; }
}

2. 更新DbContext，配置实体关系

添加实体关系配置，确保级联操作正常：

public class AppDbContext : IdentityDbContext<AppUser, IdentityRole, string>
{
     public DbSet<Book> Books { get; set; }
     public DbSet<Chapter> Chapters { get; set; }
     public DbSet<Page> Pages { get; set; }
     
     public AppDbContext(DbContextOptions options)
        : base(options)
     {
     }

     protected override void OnModelCreating(ModelBuilder modelBuilder)
     {
         base.OnModelCreating(modelBuilder);

         // 配置Book与AppUser的关联，级联删除用户时清理其书籍数据
         modelBuilder.Entity<Book>()
             .HasOne(b => b.AppUser)
             .WithMany()
             .HasForeignKey(b => b.UserId)
             .OnDelete(DeleteBehavior.Cascade);

         // 配置Chapter与Book的级联关系
         modelBuilder.Entity<Chapter>()
             .HasOne(c => c.Book)
             .WithMany(b => b.Chapters)
             .HasForeignKey(c => c.BookId)
             .OnDelete(DeleteBehavior.Cascade);

         // 配置Page与Chapter的级联关系
         modelBuilder.Entity<Page>()
             .HasOne(p => p.Chapter)
             .WithMany(c => c.Pages)
             .HasForeignKey(p => p.ChapterId)
             .OnDelete(DeleteBehavior.Cascade);
     }
}

3. 数据库迁移

执行以下命令更新数据库结构：

Add-Migration AddUserAssociationsAndCustomFields
Update-Database

4. 实现用户书籍副本创建逻辑

如果存在公共书籍模板（即原始书籍数据），需要为用户复制模板数据生成独立副本：

// 示例：从模板书籍创建用户专属书籍
public async Task<Book> CreateUserBookFromTemplate(Guid templateBookId, string currentUserId)
{
    var templateBook = await _context.TemplateBooks
        .Include(tb => tb.Chapters)
        .ThenInclude(tc => tc.Pages)
        .FirstOrDefaultAsync(tb => tb.Id == templateBookId);

    if (templateBook == null)
        throw new ArgumentException("指定的模板书籍不存在");

    // 复制模板数据到用户专属实体
    var userBook = new Book
    {
        UserId = currentUserId,
        Name = templateBook.Name,
        Description = templateBook.Description,
        Price = templateBook.Price,
        Chapters = templateBook.Chapters.Select(tc => new Chapter
        {
            Title = tc.Title,
            Description = tc.Description,
            IsCompleted = false,
            Pages = tc.Pages.Select(tp => new Page
            {
                Number = tp.Number,
                UserNotes = string.Empty,
                IsCompleted = false
            }).ToList()
        }).ToList()
    };

    _context.Books.Add(userBook);
    await _context.SaveChangesAsync();
    return userBook;
}

5. 查询用户专属数据

查询时通过UserId过滤，确保只返回当前用户的独立数据：

// 示例：获取当前用户的所有书籍及关联章节、页面
public async Task<List<Book>> GetUserBooks(string currentUserId)
{
    return await _context.Books
        .Where(b => b.UserId == currentUserId)
        .Include(b => b.Chapters)
        .ThenInclude(c => c.Pages)
        .ToListAsync();
}

方案优势 #

• 数据隔离彻底：每个用户的书籍数据完全独立，不会互相干扰
• 查询高效：通过UserId过滤，EF Core生成的SQL查询性能优异
• 扩展性强：可随时为实体添加更多自定义字段
• 操作便捷：级联配置简化了用户数据的清理工作

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