Databases
StackOverflow2013
Postsdbo
POTracking changes in Entity Framework 4.0 using POCO Dynamic Proxies across multiple data contexts
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POTracking changes in Entity Framework 4.0 using POCO Dynamic Proxies across multiple data contexts
    primarykey
    data
    text
    <p>I started messing with EF 4.0 because I am curious about the POCO possibilities... I wanted to simulate disconnected web environment and wrote the following code to simulate this:</p> <ol> <li>Save a test object in the database.</li> <li>Retrieve the test object</li> <li>Dispose of the DataContext associated with the test object I used to retrieve it</li> <li>Update the test object</li> <li>Create a new data context and persist the changes on the test object that are automatically tracked within the DynamicProxy generated against my POCO object.</li> </ol> <p>The problem is that when I call dataContext.SaveChanges in the Test method above, the updates are not applied. The testStore entity shows a status of "Modified" when I check its EntityStateTracker, but it is no longer modified when I view it within the new dataContext's Stores property. I would have thought that calling the Attach method on the new dataContext would also bring the object's "Modified" state over, but that appears to not be the case. Is there something I am missing? I am definitely working with self-tracking POCOs using DynamicProxies.</p> <pre><code>private static void SaveTestStore(string storeName = "TestStore") { using (var context = new DataContext()) { Store newStore = context.Stores.CreateObject(); newStore.Name = storeName; context.Stores.AddObject(newStore); context.SaveChanges(); } } private static Store GetStore(string storeName = "TestStore") { using (var context = new DataContext()) { return (from store in context.Stores where store.Name == storeName select store).SingleOrDefault(); } } [Test] public void Test_Store_Update_Using_Different_DataContext() { SaveTestStore(); Store testStore = GetStore(); testStore.Name = "Updated"; using (var dataContext = new DataContext()) { dataContext.Stores.Attach(testStore); dataContext.SaveChanges(SaveOptions.DetectChangesBeforeSave); } Store updatedStore = GetStore("Updated"); Assert.IsNotNull(updatedStore); } </code></pre>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. This table or related slice is empty.
    1. USRob Packwood
    plurals
    1. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    3. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POTracking changes in Entity Framework 4.0 using POCO Dynamic Proxies across multiple data contexts
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POTracking changes in Entity Framework 4.0 using POCO Dynamic Proxies across multiple data contexts
      1. USRob Packwood
      1. VTBountyStart
    3. VO
      singulars
      1. POTracking changes in Entity Framework 4.0 using POCO Dynamic Proxies across multiple data contexts
      1. This table or related slice is empty.
      1. VTUpMod
    1. COHey Rob... Have you seen the second answer on your question? Haven't heard from you since then.. I wonder what you think about it =/
      singulars
      1. POTracking changes in Entity Framework 4.0 using POCO Dynamic Proxies across multiple data contexts
      1. USArtiom Chilaru
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload