This occurs when you have a (Primary key) column that is not set to Is Identity to true in SQL and you don't pass explicit value thereof during insert. It will take the first row, then you wont be able to insert the second row, the error will pop up. This can be corrected by adding this line of code [DatabaseGenerated(DatabaseGeneratedOption.Identity)] in your PrimaryKey column and make sure its set to a data type int. If the column is the primary key and is set to IsIDentity to true in SQL there is no need for this line of code [DatabaseGenerated(DatabaseGeneratedOption.Identity)] this also occurs when u have a column that is not the primary key, in SQL that is set to Is Identity to true, and in your EF you did not add this line of code [DatabaseGenerated(DatabaseGeneratedOption.Identity)]

每个人都评论SQL，但是在EntityFramework中发生了什么?我看了整篇文章，没人能解出EF。所以几天后，我找到了一个解决方案: 在EF Core的上下文中创建模型有这样一条指令:modelBuilder。实体<客户端>(实体=>{实体。属性(e => e.d id).ValueGeneratedNever();

这也会产生错误，解决方案:你必须通过ValueGeneratedOnAdd()改变它的工作!

要非常小心地将IDENTITY_INSERT设置为ON。这是一种糟糕的实践，除非数据库处于维护模式并设置为单用户。这不仅会影响您的插入，还会影响试图访问表的其他人的插入。

为什么要在单位字段中输入一个值?

最好的解决方案是使用GeneratedValue(strategy =…)注释，即。

@Id
@GeneratedValue(strategy = GenerationType.IDENTITY)
@Column ...
private int OperationID;

它说，这个列是由数据库使用IDENTITY策略生成的，你不需要关心-数据库会做的。

不要给OperationID赋值，因为它会自动生成。试试这个:

Insert table(OpDescription,FilterID) values ('Hierachy Update',1)

如果您使用Interface并以通用方式实现savechanges方法，则会出现使用非类型化DBContext或DBSet的问题

如果这是您的情况，我建议使用强类型的dbcontext

MyDBContext.MyEntity.Add(mynewObject)

那么，保存更改就可以了