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

Hours Wasted assuming the framework could handle a complex object save(insert, or update) #17506

Closed
C-BERBER opened this issue Oct 2, 2018 — with docs.microsoft.com · 1 comment

Comments

Copy link

C-BERBER commented Oct 2, 2018

I foolishly assumed that the EF would understand based on all of the keying relationships I defined what was a new object vs what was to be updated (or even removed).

It seems to me that there should be one method that performs this for any complex model.

Having to manage the implementation above will require a lot of redundant code across multiple levels of a big data model. This is a great opportunity for a framework to shine...

If it does this somewhere else and I just haven't uncovered it please let me know.
Thanks


Document Details

Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

@ajcvickers ajcvickers transferred this issue from dotnet/EntityFramework.Docs Aug 29, 2019
@ajcvickers
Copy link
Member

Duplicate of #5536

@ajcvickers ajcvickers marked this as a duplicate of #5536 Aug 29, 2019
@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

2 participants