How to prevent DbContext from altering the database?

.net code-first database entity-framework orm

Question

I'm learning Entity Framework (currently using EF6 beta) and I'm using the code first pattern on an existing database. The entities and DbContext class are created automatically using a T4 template.

I would like to prevent the DbContext from creating / altering anything into the database at runtime.

How can I do that?

1
12
9/1/2015 3:10:02 PM

Accepted Answer

When you do enable-migrations command, you will be presented with folder /Migrations under which you can find file named Configuration.cs. Within constructor of that file, by the default, there is a property set to value:

 AutomaticMigrationsEnabled = false;

Which will ensure that your database won't be migrated automatically, but rather by invoking each migration manually.

However, if your database is larger than your domain models, i.e. you're just operating on the portion of already existing database, then somewhere in your application start (if it is ASP.NET app, Application_Start event handler), you need to add the following code:

Database.SetInitializer<YourDbContext>(null);

Otherwise, Entity Framework will complain that there is a mismatch between database definition in your domain model and actual current state of the database.

EDIT:

If you want to be sure that YourDbContext is not attempting to change database, do this:

protected override void OnModelCreating(DbModelBuilder modelBuilder) 
{ 
    throw new YourCustomException("Code first changes are not allowed."); 
}

EDIT again:

I'm trying to understand what scenario are you trying to accomplish. If you have existing database, and you want to update it but only manually, this is the approach:

  1. Use DbContext generator template to generate DbContext and entities from existing database.
  2. Run enable-migrations
  3. Do add-migration Initial
  4. Step 3 should generate empty migration if everything was done properly. You can delete it.
  5. Now whenever you do some change, you need to do add-migration ChangeName. This will not go to database, unless you do update-database.
12
9/19/2013 1:16:12 PM

Popular Answer

Set the initialiser for your context to null.

That should leave the database in it's existing state when the application starts up.

Note that you'll get an exception if you try to run the application after altering your dbContext class and/or your database schema, as your database schema will no longer match what the context expects.



Related Questions





Related

Licensed under: CC-BY-SA with attribution
Not affiliated with Stack Overflow
Licensed under: CC-BY-SA with attribution
Not affiliated with Stack Overflow