Which approach should we use database First , Code First ,Model First in MVC

Question

0.00/5 (No votes)

See more:

We are new in MVC
We are creating small prototype in MVC in less time.In this database changes may occur continuously .So which model should we use entity database first model or code first or model?Can we use mix type(Database and Code first) to achieve the result?
Thanks in advance.....

Posted 21-Jan-16 2:10am

sp_suresh

Add a Solution

2 solutions

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)

F-ES Sitecore · Answer 1 · 2016-01-21T02:31:00

The advantage of code first is that the changes to your database will be much easier and quicker...however you'll lose whatever data is in your tables every time you update your schema. If this is an issue you might want to think about doing code first. You can write routines that automatically inject data when the db is re-created, but that's obviously additional effort to bear in mind.

If there is a chance that "the prototype" is going to become "the real thing", then you'll want database first for the reasons above. You can change from code-first to db-first so it's not the end of the world, but again it's additional work to think about.

So if it's genuinely a prototype then code first is probably best.

Member 4366220 · Answer 2 · 2016-01-21T02:20:00

Solution 1

First of all, what database technology are you using...SQL Server, Oracle, Azure, Access,NoSQL,Hadoop ? . Secondly what data does the database provide. You should know these things before you even start on MVC and Entity Framework (which is not a database but essentially an ORM wrapper for ADO)

Posted 21-Jan-16 2:20am

Member 4366220

Comments

sp_suresh 21-Jan-16 8:57am

Database currently is SQL server but on production server may be Mysql.....