Unblocking duplicate foreign keys when reverse engineering an existing database (SQL Server) #25197
Labels
area-scaffolding
closed-fixed
The issue has been fixed and is/will be included in the release indicated by the issue milestone.
community-contribution
customer-reported
type-enhancement
Milestone
I frequently see this error when users of SQL Server databases reverse engineer an existing database.
One possible solution could be to let the SQL Server scaffolding factory ignore the "second" foreign key. (and maybe just log a warning)
Thoughts?
EF Core version: 5, 6
Database provider: often Microsoft.EntityFrameworkCore.SqlServer
The text was updated successfully, but these errors were encountered: