Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>I'm not sure if this can be considered a Bug. What seems to happen is that the way you manipulate the LastModified property does not trigger INotifyPropertyChanged and thus the changes do not get populated to your Database.</p> <p>To prove it use: </p> <pre><code> order2.Name = "modified order2"; ((IObjectContextAdapter)context).ObjectContext.ObjectStateManager.GetObjectStateEntry(order2).SetModifiedProperty("LastModified"); </code></pre> <p>To utilize this knowledge in your SavingChangesHandler:</p> <pre><code>private void SavingChangesHandler(object sender, EventArgs e) { DateTimeOffset now = DateTimeOffset.Now; foreach (DbEntityEntry entry in ChangeTracker.Entries() .Where(entity =&gt; entity.State == EntityState.Added || entity.State == EntityState.Modified)) { SetModifiedDate(now, entry); if (entry.State == EntityState.Modified) { ((IObjectContextAdapter) this).ObjectContext.ObjectStateManager.GetObjectStateEntry(entry.Entity).SetModifiedProperty("LastModified"); } } } </code></pre> <p><strong>Edit:</strong></p> <p>I looked into this a little more and you are correct. For some reason MS decided to not fire PropertyChanged events when using PropertyInfo.SetValue anymore. Only one way to find out if this is a bug or a design decision: File a bug report / Post to msdn Forums.</p> <p>Though changing the property directly via CurrentValue seems to work fine:</p> <pre><code>private static void SetModifiedDate(DateTimeOffset now, DbEntityEntry modifiedEntity) { if (modifiedEntity.Entity == null) { return; } modifiedEntity.Property("LastModified").CurrentValue = now; } </code></pre>
    singulars
    1. This table or related slice is empty.
    1. POEntity Framework 4.1 bug in ObjectContext.SavingChanges handling (?)
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USTill
    1. USTill
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POEntity Framework 4.1 bug in ObjectContext.SavingChanges handling (?)
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COThanks for your answer. Your suggestion actually worked! But I think it looks a little like a hack - shouldn't this be handled automatically by the framework when I modify a property? As I wrote in my question, the same code worked fine in EF4.0.
      singulars
      1. PO
      1. USJRV
    2. CO@JRV Have a look at my edit above
      singulars
      1. PO
      1. USTill
    3. COGreat - thanks again. This is a much cleaner approach, and I will go for that. I will just accept the fact that PropertyInfo.SetValue does not work anymore, now that I know the other way to do it :-)
      singulars
      1. PO
      1. USJRV
 

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