Entity states and SaveChanges in Entity FrameWork

Question

0.00/5 (No votes)

See more:

using (var context = new BloggingContext())
{
    var blog = new Blog { Name = "ADO.NET Blog" };
    context.Blogs.Add(blog);
    context.SaveChanges();
}



using (var context = new BloggingContext())
{
    var blog = new Blog { Name = "ADO.NET Blog" };
    context.Entry(blog).State = EntityState.Added;
    context.SaveChanges();
}

What was the difference between above and which will give best performance

Posted 9-Jan-14 2:20am

surendra9999999

Updated 9-Jan-14 2:21am

v2

Add a Solution

3 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)

Raul Iloc · Answer 1 · 2014-01-09T02:33:00

1.You should use the first case, because the code is more clear! As I know there is no difference between them regarding the performance.

2. In generally when you add and/or modify objects by using entity framework you should add multiple adding and changes of the objects and only when you relay finish with them to invoke "SaveCahnges()" for the entire set; in other words the "SaveChanges()" invocation should not be done to frequent for each object if is possible, and this will give you performance.

rizwan muhammed khan gouri · Answer 2 · 2014-01-21T22:23:00

Solution 2

Please visit Following Link
http://msdn.microsoft.com/en-in/data/jj592676.aspx[^]
this will gives you full information about it.

Posted 21-Jan-14 22:23pm

rizwan muhammed khan gouri

Code Help 2014 · Answer 3 · 2014-04-08T00:40:00

Solution 3

Check this sample application:

Entity Framework for Beginners[^]

Posted 8-Apr-14 0:40am

Code Help 2014

Updated 8-Apr-14 0:47am

v2