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

any plan for au "update from database" tool? #567

Closed
lucamorelli opened this issue Aug 20, 2014 · 3 comments
Closed

any plan for au "update from database" tool? #567

lucamorelli opened this issue Aug 20, 2014 · 3 comments
Milestone

Comments

@lucamorelli
Copy link

as from subject, when I use a db context with an existing db used by an existing application, happens that this application receive updates that update the db schema. I know I can update the POCO classes to reflect the new schema, but if I have updates to multiple tables a tool to do this automatically may be very useful

@rowanmiller rowanmiller added this to the Discussions milestone Aug 22, 2014
@felipepessoto
Copy link
Contributor

Its really important to have it. Since we wont have EDMX support.
I think its ok to have a EDMX like file (designer only), to keep metadata about the mapping

@rowanmiller
Copy link
Contributor

Part of this is supported already in the reverse engineer process we have in EF6 (which will be the first level of functionality we provide in EF7). You can re-reverse engineer the model and it will update the existing code. Some level of customization can be done by using partial classes etc. for any customization you make to the code (or modifying the T4 templates used during the reverse engineer process). This is far from perfect though because there are some customizations that are hard to do in a separate class without modifying the scaffolded code.

I opened these two items to track this work:

@rowanmiller
Copy link
Contributor

Closing out this issue, if you have input or concerns about either of these two scenarios please follow up on the issues linked above.

@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
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants