Entity relationships design

Question

1.00/5 (2 votes)

See more:

EF6.0

Which is better with Entity Framework , code first or database first ?

Why and when is it better?

Thank you,

C#

Posted 23-Jun-15 5:50am

Member 9168963

Add a Solution

Comments

Sergey Alexandrovich Kryukov 23-Jun-15 12:33pm

First of all, think at this:

Imagine that one of the two approaches was better in absolutely all cases. As your question doesn't provide any specific detail, we really need to consider all possible cases. Now, if one approach would really be always the best, don't you think that nobody would use another one, so it would never be mentioned?

Are you getting the idea why your question makes no sense?

—SA

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 · Accepted Answer · 2015-06-23T06:09:00

Solution 1

Code first is better when you want to write code and have a database generated that reflects that code. Database first is better when you want to design the database yourself and have the code reflect that database. So if comes down to how particular you are about the database and how important you feel its design is. I think most professionals will go with database first, even if just for the lack of hassle (when you do code first and your code changes, your database and all its data is destroyed).

Posted 23-Jun-15 6:09am

F-ES Sitecore

Comments

Andy Lanng 23-Jun-15 12:11pm

I entirely agree. Well put. 5*

Member 9168963 23-Jun-15 12:23pm

Yes both are well put. I just don't see many examples on CodeProject database first why I asked.

Database first is better for updating and easier.

Sergey Alexandrovich Kryukov 23-Jun-15 12:33pm

This is good an interesting, but first please look at my comment to the question.
—SA

F-ES Sitecore 23-Jun-15 12:36pm

I ignored the "which is better" and really answered the "when is it better". As you say, neither is "better" than the other, the better one is the one that meets your requirements.

Sergey Alexandrovich Kryukov 23-Jun-15 12:42pm

Agree, a 5. I just think that the absurdity of the question should really be mentioned, to dismiss some inquirer's illusions.
—SA

Andy Lanng · Accepted Answer · 2015-06-23T06:11:00

For Larger projects that depend on an efficient db design:
(this is 90% of the dbs I have written)

I recommend pen and paper :S

The process good of DB design goes through several iterations of normalization and de-normalization. I find it useful to organize my db way before I start writing it.

I would then write the database first. There are several reasons for this but the best one is that I will just drag-drop into the dbml.

I will usually do that one table at a time. Personally, I don't think that any links should cross over each other, so I do this to prove my case.

I have been designing dbs for well over a decade so I can visualize the end result to a huge extent when I am designing and implementing it. You may find it easier to start with the EF model first so that you can visualize it better, but I find making tweaks and changes on the DB much easier and quicker that editing it from the EF models.

For smaller dbs or where query and data efficiency is not a priority
(such as basic content websites or just to handle global settings for eg)

Well, whatever is convenient. It isn't worth spending too much time on the design. If you know what tables are needed then you can easily create the EF first.

If you are likely to edit the database then I would swing more to the db first approach, unless changes are minor.

When handing over a small project to a junior, it would be best to have the EF first approach as this is easy to implement for anyone who accesses your source.

That's just IMHO ^_^

EDIT: Updated with Sergeys comments in mind