You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I created a working project with EF Core 1.2 by generating a data model with EF Scaffolding. This project worked fine under version 1.2. When version 2.0 was released I updated the EF project to the latest version, but immediately started to expierence stackoverflow messages when loading the DbContext.
I've investigated the problem and it seems the problem is due to two bad foreign key contraints in our
sql server database. The contraints looked like: [Table].[Id] => [Table].[Id] (e.g. [Foo].[Id] => [Foo].[Id]), so basicly the id field was referencing itself in the same table. I think this happens when someone adds a foreign key by accident and doesn't configure it in sql server management studio.
The text was updated successfully, but these errors were encountered:
wielvanraaij
changed the title
Stackoverflow after migration EF Core from 1.x to 2.0
Stack overflow after migration EF Core from 1.2 to 2.0
Aug 23, 2017
Hi @wielvanraaij. We are gathering information on the use of EF Core pre-release builds. You reported this issue shortly after the release of 2.0.0 RTM. It would be really helpful if you could let us know:
Did you consider testing your code against the pre-release builds?
Was there anything blocking you from using pre-release builds?
What do you think could make it easier for you to use pre-release builds in the future?
Thanks in advance for any feedback. Hopefully this will help us to increase the value of pre-release builds going forward.
I created a working project with EF Core 1.2 by generating a data model with EF Scaffolding. This project worked fine under version 1.2. When version 2.0 was released I updated the EF project to the latest version, but immediately started to expierence stackoverflow messages when loading the DbContext.
I've investigated the problem and it seems the problem is due to two bad foreign key contraints in our
sql server database. The contraints looked like: [Table].[Id] => [Table].[Id] (e.g. [Foo].[Id] => [Foo].[Id]), so basicly the id field was referencing itself in the same table. I think this happens when someone adds a foreign key by accident and doesn't configure it in sql server management studio.
The text was updated successfully, but these errors were encountered: