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 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.
ID: 130521ba-2943-c640-4190-7e22af37e154
Version Independent ID: c31908e9-2836-8efd-5df6-e9dc5b5a9a5f
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.
The text was updated successfully, but these errors were encountered: