All Records got deleted because of Database Drop in code first approach in MVC

Question

0.00/5 (No votes)

See more:

Hello,

as all EF creates database,table and column according our class created in front-end automatically in code first approach.

So, i added one more extra coloumn in my class after creating Data base ,table and column.

But, i got the following exception .

An exception of type 'System.InvalidOperationException' occurred in EntityFramework.dll but was not handled in user code

Additional information: The model backing the 'MvcMusicStoreContext' context has changed since the database was created. Consider using Code First Migrations to update the database (http://go.microsoft.com/fwlink/?

this is because of Migration.

so, i added the follow line in Global.asax.cs(Application_Start) to fix that exception.

Database.SetInitializer(new DropCreateDatabaseIfModelChanges<employeedbcontext>());

now works fine.

But the problem my existing database and table values got dropped and creates new as new with empty . i mean there is just column name only available.

is that good in MVC? how can i fix this problem.

Posted 17-Nov-14 0:06am

christhuxavier

Add a Solution

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Nathan Minier · Answer 1 · 2014-11-17T02:52:00

The route that you took is an initialization strategy, and it is behaving in the expected manner. You don't want to use it for a production database, what you'll want to use instead is a Migration.

Code First migrations are described in detail at:
http://msdn.microsoft.com/en-us/data/jj591621.aspx[^]

You can also write your own initialize, but I would not go down that route unless you want to start getting into the weeds of how EF interacts with the database.

The most important lesson here: migrations != initialization strategy