Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Stack overflow after migration EF Core from 1.2 to 2.0 #9534

Closed
wielvanraaij opened this issue Aug 23, 2017 · 3 comments
Closed

Stack overflow after migration EF Core from 1.2 to 2.0 #9534

wielvanraaij opened this issue Aug 23, 2017 · 3 comments

Comments

@wielvanraaij
Copy link

wielvanraaij commented Aug 23, 2017

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.

@wielvanraaij 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
@seb999
Copy link

seb999 commented Aug 23, 2017

We are facing the same issue here:
#9462

@ajcvickers
Copy link
Contributor

Duplicate of #9478

@ajcvickers ajcvickers marked this as a duplicate of #9478 Aug 23, 2017
@ajcvickers
Copy link
Contributor

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.

@ajcvickers ajcvickers reopened this Oct 16, 2022
@ajcvickers ajcvickers closed this as not planned Won't fix, can't repro, duplicate, stale Oct 16, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants