More streamlined workflow for early stage app development

While developing a new app, nobody’s using my local database other than me, so the only migration I need is the initial one. The process involves writing some code, blowing away the old state of the database and associated migrations, then generating new ones and applying them back to the database. It sure would be nice to be able to do this literally in one step.

e.g. Something like dnx ef rebuild-all and have it destroy the existing migrations, unapply them from the database, generate new migrations and apply those to the database.

[bricelam]

I was thinking more about what this might look like today. Imagine if we allowed one temporary, non-destructive, automatic migration locally.

First, it is 100% local. It should never be shared with other team members. It could be stored in the local database. It might be stored as a temporary file somewhere for perf.

It can mutate. Just like automatic migrations in EF6, it would evolve change-to-change without any user interaction. You just change your domain model and it will diff against your local database (or maybe just the last migration) to bring your schema up to date.

It should be non-destructive. You should be able to take the schema back to the previous non-temporary migration without losing any data. Maybe instead of dropping columns and tables, it just makes required columns and foreign keys nullable instead.

It must eventually be reverted. We could do this automatically when adding or applying any migrations. Adding a migration would essentially “commit” all the changes you’ve done into a single migration.

…just some rough ideas I wanted to jot down.

[fadialjabali]

hey @bricelam , do you think this can be added at some point ?