c# - AspNet Identity - 重复外键的自定义 IdentityRoleClaim & IdentityUserRole & IdentityUserClaim
问题描述
目前,我正在使用 AspNetCore 和配置 dbcontext,如下所示:
public class AppDbContext : IdentityDbContext<ApplicationUser, ApplicationRole, string, ApplicationUserClaim, ApplicationUserRole, IdentityUserLogin<string>, ApplicationRoleClaim, IdentityUserToken<string>>
{
public AppDbContext(DbContextOptions<AppDbContext> options)
: base(options)
{ }
所以我想自定义 AspNetIdentity,但为简单起见,我刚刚在表之间配置了外键:
- ApplicationUser 派生自 IdentityUser
- ApplicationRole 派生自 IdentityRole
- ApplicationUserClaim 派生自 IdentityUserClaim
<string>
- ApplicationUserRole 派生自 IdentityUserRole
<string>
- ApplicationRoleClaim 派生自 IdentityRoleClaim
<string>
public class ApplicationUser : IdentityUser
{
public virtual ICollection<ApplicationUserRole> UserRoles { get; set; }
public virtual ICollection<ApplicationUserClaim> UserClaims { get; set; }
}
public class ApplicationRole : IdentityRole
{
public virtual ICollection<ApplicationUserRole> UserRoles { get; set; }
public virtual ICollection<ApplicationRoleClaim> RoleClaims { get; set; }
}
public class ApplicationRoleClaim : IdentityRoleClaim<string>
{
public virtual ApplicationRole Role { get; set; }
}
public class ApplicationUserRole : IdentityUserRole<string>
{
public int Id { get; set; }
public virtual ApplicationRole Role { get; set; }
public virtual ApplicationUser User { get; set; }
}
public class ApplicationUserClaim : IdentityUserClaim<string>
{
public virtual ApplicationUser User { get; set; }
}
以下是派生类为特定的自定义身份模型实现 IEntityTypeConfiguration。
public class ApplicationUserEntityBuilder : IEntityTypeConfiguration<ApplicationUser>
{
public void Configure(EntityTypeBuilder<ApplicationUser> builder)
{
// still use default table name
builder.ToTable("AspNetUsers");
builder.Property(p => p.Id)
.HasColumnType("CHAR(36)");
}
}
public class ApplicationRoleEntityBuilder : IEntityTypeConfiguration<ApplicationRole>
{
public void Configure(EntityTypeBuilder<ApplicationRole> builder)
{
// still use default table name
builder.ToTable("AspNetRoles");
}
}
public class ApplicationUserClaimEntityBuilder : IEntityTypeConfiguration<ApplicationUserClaim>
{
public void Configure(EntityTypeBuilder<ApplicationUserClaim> builder)
{
builder.Property(p => p.UserId)
.HasColumnName(nameof(ApplicationUserClaim.UserId))
.HasColumnType("CHAR(36)");
builder.HasOne(p => p.User)
.WithMany(u => u.UserClaims)
.HasForeignKey(p => p.UserId)
.IsRequired();
}
}
public class ApplicationUserRoleEntityBuilder : IEntityTypeConfiguration<ApplicationUserRole>
{
public void Configure(EntityTypeBuilder<ApplicationUserRole> builder)
{
// still use default table name
builder.ToTable("AspNetUserRoles");
builder.HasKey(p => p.Id);
builder.Property(p => p.Id)
.ValueGeneratedOnAdd();
builder.HasOne(p => p.Role)
.WithMany(r => r.UserRoles)
.HasForeignKey(p => p.RoleId)
.IsRequired();
builder.HasOne(p => p.User)
.WithMany(r => r.UserRoles)
.HasForeignKey(p => p.UserId)
.IsRequired();
}
}
public class ApplicationRoleClaimEntityBuilder : IEntityTypeConfiguration<ApplicationRoleClaim>
{
public void Configure(EntityTypeBuilder<ApplicationRoleClaim> builder)
{
// still use default table name
builder.ToTable("AspNetRoleClaims");
builder.HasKey(p => p.Id);
builder.Property(p => p.Id)
.ValueGeneratedOnAdd();
builder.Property(p => p.RoleId)
.HasColumnName(nameof(ApplicationRoleClaim.RoleId))
.HasColumnType("CHAR(36)");
builder.HasOne(p => p.Role)
.WithMany(r => r.RoleClaims)
.HasForeignKey(p => p.RoleId)
.IsRequired();
}
}
在这些所有流畅的 API 配置之后,EF Core 在表 AspNetRoleClaims、AspNetUserClaims、AspNetUserRoles 中生成了重复的外键
migrationBuilder.CreateTable(
name: "AspNetRoleClaims",
columns: table => new
{
Id = table.Column<int>(nullable: false)
.Annotation("SqlServer:ValueGenerationStrategy", SqlServerValueGenerationStrategy.IdentityColumn),
RoleId = table.Column<string>(type: "CHAR(36)", nullable: false),
ClaimType = table.Column<string>(nullable: true),
ClaimValue = table.Column<string>(nullable: true),
RoleId1 = table.Column<string>(nullable: true) // DUPLICATE
},
constraints: table =>
{
table.PrimaryKey("PK_AspNetRoleClaims", x => x.Id);
table.ForeignKey(
name: "FK_AspNetRoleClaims_AspNetRoles_RoleId",
column: x => x.RoleId,
principalTable: "AspNetRoles",
principalColumn: "Id",
onDelete: ReferentialAction.Cascade);
table.ForeignKey(
name: "FK_AspNetRoleClaims_AspNetRoles_RoleId1",
column: x => x.RoleId1,
principalTable: "AspNetRoles",
principalColumn: "Id",
onDelete: ReferentialAction.Restrict);
});
migrationBuilder.CreateTable(
name: "AspNetUserClaims",
columns: table => new
{
Id = table.Column<int>(nullable: false)
.Annotation("SqlServer:ValueGenerationStrategy", SqlServerValueGenerationStrategy.IdentityColumn),
UserId = table.Column<string>(type: "CHAR(36)", nullable: false),
ClaimType = table.Column<string>(nullable: true),
ClaimValue = table.Column<string>(nullable: true),
UserId1 = table.Column<string>(nullable: true) //DUPLICATE
},
constraints: table =>
{
table.PrimaryKey("PK_AspNetUserClaims", x => x.Id);
table.ForeignKey(
name: "FK_AspNetUserClaims_AspNetUsers_UserId",
column: x => x.UserId,
principalTable: "AspNetUsers",
principalColumn: "Id",
onDelete: ReferentialAction.Cascade);
table.ForeignKey(
name: "FK_AspNetUserClaims_AspNetUsers_UserId1",
column: x => x.UserId1,
principalTable: "AspNetUsers",
principalColumn: "Id",
onDelete: ReferentialAction.Restrict);
});
migrationBuilder.CreateTable(
name: "AspNetUserRoles",
columns: table => new
{
UserId = table.Column<string>(nullable: false),
RoleId = table.Column<string>(nullable: false),
Id = table.Column<int>(nullable: false)
.Annotation("SqlServer:ValueGenerationStrategy", SqlServerValueGenerationStrategy.IdentityColumn),
RoleId1 = table.Column<string>(nullable: true), //DUPLICATE
UserId1 = table.Column<string>(nullable: true) //DUPLICATE
},
constraints: table =>
{
table.PrimaryKey("PK_AspNetUserRoles", x => new { x.UserId, x.RoleId });
table.UniqueConstraint("AK_AspNetUserRoles_Id", x => x.Id);
table.ForeignKey(
name: "FK_AspNetUserRoles_AspNetRoles_RoleId",
column: x => x.RoleId,
principalTable: "AspNetRoles",
principalColumn: "Id",
onDelete: ReferentialAction.Cascade);
table.ForeignKey(
name: "FK_AspNetUserRoles_AspNetRoles_RoleId1",
column: x => x.RoleId1,
principalTable: "AspNetRoles",
principalColumn: "Id",
onDelete: ReferentialAction.Restrict);
table.ForeignKey(
name: "FK_AspNetUserRoles_AspNetUsers_UserId",
column: x => x.UserId,
principalTable: "AspNetUsers",
principalColumn: "Id",
onDelete: ReferentialAction.Cascade);
table.ForeignKey(
name: "FK_AspNetUserRoles_AspNetUsers_UserId1",
column: x => x.UserId1,
principalTable: "AspNetUsers",
principalColumn: "Id",
onDelete: ReferentialAction.Restrict);
});
如果我做错了什么,请为我检查。提前谢谢你们。
更新 1
因为导航属性会导致重复的外键。如果我在自定义身份模型中删除这些属性,EFCore 将不会生成“DuplicateProperty1”。那我现在该怎么办?
最后更新
base.OnModelCreating(builder);
我放在方法末尾的根本原因protected override void OnModelCreating(ModelBuilder builder)
。因此,我配置的任何内部派生类都实现了 IEntityTypeConfiguration,它将被基类覆盖。最终版本如下:
public class AppDbContext : IdentityDbContext<ApplicationUser, ApplicationRole, string, ApplicationUserClaim, ApplicationUserRole, IdentityUserLogin<string>, ApplicationRoleClaim, IdentityUserToken<string>>
{
public AppDbContext(DbContextOptions<AppDbContext> options)
: base(options)
{ }
protected override void OnModelCreating(ModelBuilder builder)
{
base.OnModelCreating(builder);
var entitiesBuilder = Assembly.GetExecutingAssembly()
.GetTypes()
.Where(type => type.ContainsGenericParameters == false && type.GetInterface(nameof(IEntityBuilder)) != null)
.ToList();
foreach (var entityBuilder in entitiesBuilder)
{
var instance = Activator.CreateInstance(entityBuilder) as IEntityBuilder;
instance.RunConfiguration(builder);
}
// base.OnModelCreating(builder); move this line to the beginning of this method
}
}
解决方案
表之间的关系已经在Identity 的 IdentityDbContext
默认配置中设置。这意味着您不必明确指定它们(使用导航道具/流畅的 api 配置)。
但是,您似乎希望使用 Guid/Uuid 而不是字符串作为主键/外键的列类型。如果是这种情况,实现这一目标的正确方法是使用您已经继承的类的泛型变体。
例如,您可以只定义需要扩展的类并向它们添加其他属性 - 这将包含在 DB Migration 中:
public class ApplicationUser : IdentityUser<Guid>
{
}
public class ApplicationRole : IdentityRole<Guid>
{
}
除此之外,您DbContext
必须继承以下的正确变体IdentityDbContext
:
public class ApplicationUserDbContext : IdentityDbContext<ApplicationUser, ApplicationRole, Guid>
{
}
之后,您的迁移将生成一个脚本以将 PK/FK 更改为正确的列类型。如果您需要从Identity扩展其他类型,您可以使用最通用的变体,IdentityDbContext
它带有一堆类型参数。
推荐阅读
- python - 将 Keras 集成到 SKLearn 管道?
- python-3.x - 如何使用这种数据集格式创建和弦图?
- python - 我想用 python 求解一个线性方程:LinAlgError 奇异矩阵
- c++ - 如何定义凭据提供程序使用场景
- ios - 如何修复此代码以允许计时器在用户单击 UIAlert 时启动?
- ksqldb - 空的 KSQL 流
- sql - PostgreSQL 删除视图(如果存在)
- excel-formula - 使用拆分分隔字符串的公式获取#value
- c++ - 如何使用 C++ 接口从 AVRO 文件中读取数据?
- android - Android 发布构建期间的 bundleReleaseJsAndAssets 花费了无限时间