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

Implement CurrentValues, OriginalValues, and GetDatabaseValues on EntityEntry #1200

Closed
ajcvickers opened this issue Dec 2, 2014 · 5 comments
Labels
closed-fixed The issue has been fixed and is/will be included in the release indicated by the issue milestone. type-enhancement
Milestone

Comments

@ajcvickers
Copy link
Contributor

No description provided.

@ghost
Copy link

ghost commented Jul 16, 2016

when will this feacture be implemented? I need it for a update function in an update method in a service (N-Tire architecture).

@ajcvickers
Copy link
Contributor Author

@leo90skk Current plan of record is to implement in 1.1, but that could change.

@ajcvickers ajcvickers modified the milestones: 1.1.0, Backlog Jul 18, 2016
@rowanmiller
Copy link
Contributor

Currently planned for 1.1 - see https://blogs.msdn.microsoft.com/dotnet/2016/07/29/entity-framework-core-1-1-plans/ for details.

ajcvickers added a commit that referenced this issue Aug 17, 2016
Issue #1200

Pretty much the same design as EF6. Exposed full property metadata instead of names since we now have nice metadata. Tests were ported from EF6. Not fully functional, especially on SqLite, until #6337 is fixed.
ajcvickers added a commit that referenced this issue Aug 19, 2016
Issue #1200

Pretty much the same design as EF6. Exposed full property metadata instead of names since we now have nice metadata. Tests were ported from EF6. Not fully functional, especially on SqLite, until #6337 is fixed.
@ajcvickers ajcvickers added the closed-fixed The issue has been fixed and is/will be included in the release indicated by the issue milestone. label Aug 19, 2016
@dstep2007
Copy link

I see 1.1 was just released. Did this make it into the release?

@smitpatel
Copy link
Contributor

@dstep2007 - Yes.

@ajcvickers ajcvickers modified the milestones: 1.1.0-preview1, 1.1.0 Oct 15, 2022
@ajcvickers ajcvickers removed their assignment Sep 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
closed-fixed The issue has been fixed and is/will be included in the release indicated by the issue milestone. type-enhancement
Projects
None yet
Development

No branches or pull requests

4 participants