Last post Sep 13, 2016 07:38 PM by superjose
Sep 10, 2016 04:58 PM|superjose|LINK
Hello everybody. This is the third time that I swipe the database completely (Development), and second time I do (production). As you may have guessed, production data isn't that important right now. But in the following months, I can't have the luxury of
I'm using Entity Framework 6.1 w/ Migrations, the following scenarios have occurred:
- Development Database and Production DB are out-of-sync (this is natural). Problem: I may have accidentally deleted a migration file. So there's a big gap between the jumps that the migrations need to do, and the actual data. Current solution I know is
to compare Table schemes, and manually modify at production (Solution is error prone).
- I have a complex class, which have been moved to become child of another complex class. Is there a way, besides manually querying the db, for moving all the data to the current one?
- What is the best approach (Either Design Patterns, DBMS, etc.) for an always-changing schema while preventing data-loss? (There are things that are refactored kind of quickly, so the schema is always prone to change.
Sep 12, 2016 02:02 PMemail@example.com|LINK
I suggest you could refer to follow link to know more about
Code First Migrations with an existing database
Sep 13, 2016 07:38 PM|superjose|LINK
Thanks for the overview!! :D