Databases
StackOverflow2013
Postsdbo
POHow to deal with faulted objects returned by fetchedResultsController when the returned object may also be deleted from the persistent store
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POHow to deal with faulted objects returned by fetchedResultsController when the returned object may also be deleted from the persistent store
    primarykey
    data
    text
    <ol> <li>In my simple experiments it doesn't seem that the fetchedResultsController is returning faulted objects. Is it possible for the fetchedResultsController to return a faulted Core Data object for a specific index path?</li> <li>The sample code below runs on the main thread. Lets say that at "Point A" a background thread deletes and saves to the persistent store the object that was just returned by the fetched results controller. Now when we attempt to access properties on the <code>dataObject</code> we crash because the fault cannot be fulfilled since the data has been deleted from the persistent store.</li> <li>One thing I have seen is that the relationships are more likely to be faulted. So instead at "Point A" lets say that the parent object is deleted from the persistent store. Then when attempting to access the name property on the parent an error will occur since a fault cannot be fulfilled.</li> <li>What is the best way to prevent this sort of problem?</li> </ol> <p>Sample code:</p> <pre><code>- (UITableViewCell *)tableView:(UITableView *)tableView cellForRowAtIndexPath:(NSIndexPath *)indexPath { UITableViewCell *cell = code_for_cell_reuse_here; PersonModelObject *dataObject = (PersonModelObject *)[self.fetchedResultsController objectAtIndexPath:indexPath]; /* Point A */ cell.textLabel.text = dataObject.name; cell.detailTextLabel.text = dataObject.parent.name; return cell; } </code></pre>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USEvan
    1. USEvan
    plurals
    1. This table or related slice is empty.
    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. POHow to deal with faulted objects returned by fetchedResultsController when the returned object may also be deleted from the persistent store
      1. USEvil Nodoer
      1. VTFavorite
    2. VO
      singulars
      1. POHow to deal with faulted objects returned by fetchedResultsController when the returned object may also be deleted from the persistent store
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POHow to deal with faulted objects returned by fetchedResultsController when the returned object may also be deleted from the persistent store
      1. This table or related slice is empty.
      1. VTUpMod
    1. This table or related slice is empty.
 

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