EF architecture ~ The timestamp field in mysql is considered as primary key auto-increment, efmysql

EF architecture ~ The timestamp field in mysql is considered as primary key auto-increment, efmysql

Back to directory

If an auto-increment field is added to mysql to maintain the row version, an error occurs in EF, which is treated as the primary key of the data table, when your real primary key is from the past, the default value 0 will be spelled into the generated SQL statement, leading to your insert error. This is the reason!

We need to comment it out. After commenting, there are new problems.

This kind of problem is also very boring!

This problem occurs because the CreateDate field in your MySQL database does not remove the timestamp. You should just remove it first!

Run the program again to solve the problem!

Back to directory