Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 1022719
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 16, 20262026-05-16T11:30:27+00:00 2026-05-16T11:30:27+00:00

I am trying to implement an UnitOfWork type pattern where one DataContext is used

  • 0

I am trying to implement an UnitOfWork type pattern where one DataContext is used over a short group of related methods and only at the end do I save the changes. However, I have found that entities added to the ObjectContext do seem to be available for reselection unless I SaveChanges, which is what I am trying to avoid. Can someone tell me if this is the expected behaviour? I have provided a psuedo test to illustrate:

    [Test]
    public void ObjectContext_ShouldSelectBackUncommitedValuesWhenUsingTheSameContext()
    {
        //arrange
        var entityConnectionString = "MyEntityConnectionString";
        var dataContext = new MyObjectContext(entityConnectionString);

        var personCount = dataContext.People.AsQueryable<Person>().Count();
        var person = new Person() { Name = "Bob" };

        //act
        dataContext.AddToPeople(person);

        //assert
        var actualPerson = dataContext.People.AsQueryable<Person>().Where(p => p.Name == "Bob").FirstOrDefault();
        Assert.IsTrue(actualPerson != null,"Uncommitted Person should return when using same context");

        var actualCount = dataContext.People.AsQueryable<Person>().Count();
        Assert.IsTrue(actualCount == personCount + 1, String.Format("Expected {0} people but got {1} people", personCount + 1, actualCount));

        //leave transaction to rollback

    }

This test fails with the actualPerson being null and the Count of the People set not incrementing. Forgive me if there are any typos as I have just simplified my own ObjectContext.

FYI I am using EF 4.

TIA.

–EDIT–
Further by way of analogy, I was hoping to be able to work with uncommitted objects as I can in SQL eg:

CREATE TABLE Person (Name nvarchar(10));
INSERT INTO Person VALUES ('Francois')
INSERT INTO Person VALUES ('Hans')

SELECT COUNT(*) FROM Person

BEGIN TRANSACTION
INSERT INTO Person VALUES ('Bob')
SELECT 'Bob Lives!' WHERE EXISTS(SELECT * FROM Person WHERE NAME='Bob')
ROLLBACK TRANSACTION

DROP TABLE Person
  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-05-16T11:30:27+00:00Added an answer on May 16, 2026 at 11:30 am

    Doing this

    dataContext.People.AsQueryable<Person>().Where(p => p.Name == "Bob").FirstOrDefault();
    

    actually results in a database call, so it shouldn’t return any unpersisted data.
    If you want to get your person back, you have to use ObjectStateManager:

    dataContext.ObjectStateManager.
               GetObjectStateEntries(EntityState.Added | EntityState.Deleted | 
                                     EntityState.Modified | EntityState.Unchanged).
               Where(ent => ent.Entity is Person).
               Select(ent => ent.Entity as Person).
               Where(p => p.Name == "Bob").
               FirstOrDefault();
    
    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.