基于Identity与EF Code-First的MVC/Web API应用用户关系设计问询

Got it, let's walk through exactly how to implement your requirements without extra tables or relationship objects. Here's a step-by-step breakdown:

1. Modify the ApplicationUser Class #

First, update your ApplicationUser to include the foreign key for the parent user and the collection of child users. This creates a self-referential relationship directly in the AspNetUsers table:

public class ApplicationUser : IdentityUser
{
    // Foreign key linking to the parent user (nullable since not all users have a parent)
    public string? ParentId { get; set; }

    // Optional navigation property to access the parent user (remove if you don't need it)
    public virtual ApplicationUser? Parent { get; set; }

    // Your required collection of child users
    public virtual ICollection<ApplicationUser> Children { get; set; } = new List<ApplicationUser>();
}

2. Configure the Relationship in EF Core #

Next, tell Entity Framework how to map this self-referential relationship by updating your ApplicationDbContext's OnModelCreating method. This ensures EF generates the correct foreign key constraint and avoids cascade delete issues with Identity tables:

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

    protected override void OnModelCreating(ModelBuilder builder)
    {
        base.OnModelCreating(builder); // Always call the base Identity configuration first

        // Configure the parent-child self-referential relationship
        builder.Entity<ApplicationUser>()
            .HasMany(u => u.Children) // A user can have many children
            .WithOne(u => u.Parent) // Each child has one parent
            .HasForeignKey(u => u.ParentId) // Use ParentId as the foreign key
            .OnDelete(DeleteBehavior.Restrict); // Prevent cascade delete to avoid accidental data loss
    }
}

3. Update the Database with Code-First Migrations #

Now generate and apply the migration to add the ParentId column to your AspNetUsers table:

1. Open the Package Manager Console (Tools > NuGet Package Manager > Package Manager Console)
2. Run this command to create a migration:

   Add-Migration AddParentChildRelationshipToAspNetUsers
   

3. Apply the migration to update your database:

   Update-Database
   

4. Use the Relationship in Your Code #

You can now work with the parent-child relationship directly through the ApplicationUser properties. Here are some common examples:

Fetch a User with Their Children #

// Inject UserManager<ApplicationUser> into your controller/service
private readonly UserManager<ApplicationUser> _userManager;

public YourController(UserManager<ApplicationUser> userManager)
{
    _userManager = userManager;
}

public async Task<IActionResult> GetUserWithChildren(string userId)
{
    var user = await _userManager.Users
        .Include(u => u.Children) // Eager load the children collection
        .FirstOrDefaultAsync(u => u.Id == userId);

    if (user == null)
    {
        return NotFound();
    }

    // Access user.Children to get all associated child users
    return Ok(new { User = user, Children = user.Children });
}

Assign a Parent to a Child User #

public async Task<IActionResult> SetParent(string childId, string parentId)
{
    var childUser = await _userManager.FindByIdAsync(childId);
    var parentUser = await _userManager.FindByIdAsync(parentId);

    if (childUser == null || parentUser == null)
    {
        return NotFound("User not found");
    }

    childUser.ParentId = parentUser.Id;
    var result = await _userManager.UpdateAsync(childUser);

    if (result.Succeeded)
    {
        return Ok("Parent assigned successfully");
    }

    return BadRequest(result.Errors);
}

Key Notes #

• No extra tables are created: All relationships are stored directly in the AspNetUsers table via the ParentId column.
• The relationship is fully compatible with Identity: You're extending the default ApplicationUser without breaking any existing Identity functionality.
• The Parent navigation property is optional—you can remove it if you only need to access a user's children and not their parent.

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