title: Forcing Core Data to refresh an NSManagedObject from a previous stored version when an updated version is already in memory
body: <p>I'm having trouble forcing Core Data to refresh some of my NSManagedObject subclasses in a document based iOS app I'm writing.</p>
  
  <p>The problem is in dealing with the situation where the user loads a second document while there are unsaved changes in the current document
  At the moment, if the user loads the first document again, the unsaved changes show up.
  The documents are loaded using an NSFetchRequest for the document's root object. This fetch request has the property <code>-setShouldRefreshRefetchedObjects:</code> set to <code>YES</code> and the property
   <code>-setIncludesPendingChanges:</code> set to <code>NO</code> I'm certain that they aren't being saved to the persistent store, since terminating the app and restarting it causes the original unaltered document to show up.  Also, I have SQL debug turned on, and it shows that the app isn't fetching from the relevant tables the second time around</p>