EF Core Fluent API可映射用户集合

时间:2018-12-24 14:07:06

标签: c# entity-framework-core ef-fluent-api

我有一个Notification类

public class Notification
{
    public int NotificationId { get; set; }

    public string NotificationMessage { get; set; }
    public DateTime NotificationSentOn { get; set; }

    //TODO: not sure how to map this in fluent api
    // a Notification can go to many users
    public ICollection<ApplicationUser> ReceivingUsers { get; set; }
}

和ApplicationUser的扩展名

public class ApplicationUser : IdentityUser
{
    public ApplicationUser()
    {
        IsAuthor = false;
    }
    public string Firstname { get; set; }
    public string Lastname { get; set; }
    public Gender Gender { get; set; }
    public DateTime? DateOfBirth { get; set; }
    public DateTime RegisteredDate { get; set; }
    public bool IsAuthor { get; set; }

    // foreign key to UserProfile using the string ID from ApplicationUser
    public UserProfile MemberProfile { get; set; }
    // collection of notifications for this user
    public ICollection<Notification> Notifications { get; set; }
}

这是与ApplicationUser类中的Notifications属性有关的错误

  

无法确定类型为“ ICollection”的导航属性“ ApplicationUser.Notifications”表示的关系。要么手动配置关系,要么使用“ [NotMapped]”属性或“ OnModelCreating”中的“ EntityTypeBuilder.Ignore”忽略此属性。

我认为这种关系应该是一对多的,即一个通知会发送给许多ApplicationUser,但是我在Entity中的正常模式 配置不起作用,我必须在其中一个类中缺少某些内容。

我不确定如何使用流畅的API将Notifications集合或外键关系映射到UserProfile(我正在通过IEntityTypeConfiguration接口使用EntityConfiguration类)

更新 按照卡米洛的回答,我更新了“实体配置”,使其包含NavigationUser表,该表将主键设置如下,

public class NotificationUserEntityConfiguration : IEntityTypeConfiguration<NotificationUser>
{
    public void Configure(EntityTypeBuilder<NotificationUser> builder)
    {
        builder.HasKey(u => new { u.ApplicationUserId, u.NotificationId })
            .HasName("PK_NotificationUser");

        builder.Property(u => u.NotificationId)
            .ValueGeneratedNever()
            .IsRequired();            

        builder.Property(u => u.ApplicationUserId)
            .ValueGeneratedNever()
            .IsRequired();

    }
}

这从数据库创建脚本返回了以下内容

它在ApplicationUser表中创建了一个ForeignKey

table.ForeignKey(                        name: "FK_AspNetUsers_Notifications_NotificationId",
        column: x => x.NotificationId,
        principalSchema: "MachineryCtx",
        principalTable: "Notifications",
        principalColumn: "NotificationId",
        onDelete: ReferentialAction.Restrict);

和NotificationUsers表中的ForeignKey返回通知

table.ForeignKey(                       name: "FK_NotificationUser_Notifications_NotificationId",
      column: x => x.NotificationId,
      principalSchema: "MachineryCtx",
      principalTable: "Notifications",
      principalColumn: "NotificationId",
      onDelete: ReferentialAction.Cascade);

1 个答案:

答案 0 :(得分:1)

您正在尝试将多对多关系建模为一对多关系。

您应该改成这样:

public class ApplicationUser
{
    ...
    public ICollection<NotificationUser> Notifications { get; set; }
}

public class Notification
{
    ...
    public ICollection<NotificationUser> Users { get; set; }
}

public class NotificationUser
{
    public int ApplicationUserId { get; set; }
    public int NotificationId { get; set; }

    public ApplicationUser User { get; set; }
    public Notification Notification { get; set; }
}

说:

  • 用户可以收到很多通知
  • 一个通知可以有很多用户

您既可以使用IDENTITY主键,也可以使用带有ApplicationUserId,NotificationId的复合主键