Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>You have the basic idea, so there is probably a bug somewhere in your code...</p> <p>Double check that you are properly registering to receive the notification from the background MOC.</p> <p>Register to receive all notifications from all objects. In that method, log the event, and all its data. When the object is a MOC, dump all its properties (especially the lists of registered, inserted, updated, and deleted objects).</p> <p>Put a log statement right before and after the save call, and in the notification handler for merging the notification.</p> <p>Also, you omitted a lot of code so it's hard to know what you are actually doing, but the code sample you included looks like it is hard setting isSync to YES for all objects being loaded, but your fetch request only wants those with isSync set to NO. None of those new objects will pass that predicate.</p> <p>Finally, double check your model definition and make sure you are using the right number type. This can be a big source of problems.</p> <p><strong>EDIT</strong></p> <p>Oh yeah, I forgot... your fetch request does not have a sort descriptor. When you create a FRC, your fetch request must contain at least one sort descriptor... if you have multiple sections, the first sort descriptor is used to group the objects into sections.</p> <p>To follow up on Alexsander's comment... I alluded to it at the beginning of my post, but you certainly do not want to listen to notifications from a MOC unless it is well known as one of yours (unless, of course, you are just logging for debugging purposes). You should know about the MOC you are using.</p> <p>Furthermore, I would suggest using parent/child MOCs for this type of processing, but what you are doing should work if done properly.</p> <p>Parent (private concurrency type) Main (main concurrency type)</p> <p>Then, with your background MOCs, just have them set the main moc as their parent. When they save, their objects get injected directly into the main MOC. The main MOC can then issues saves at later times to put them onto disk.</p> <p>Or, you can parent you background MOC to the "parent" and then the "main" MOC can just reissue the fetch to get the data from the parent.</p>
    singulars
    1. This table or related slice is empty.
    1. PONSFetchedResultsController doesn't show updates from a different context
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USJody Hagins
    1. USJody Hagins
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PONSFetchedResultsController doesn't show updates from a different context
      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. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COMany frameworks use Core Data internally. Make sure you don't merge those notifications by mistake.
      singulars
      1. PO
      1. USAlexsander Akers
    2. CO@JodyHagins First of all thank you for your answer. + 1 for your support. What I wrote in the edit, I think, it's not a problem. Maybe I've changed something but I don't know what. Could you explain what do you mean with *...but the code sample you included looks like it is hard setting isSync to YES for all objects being loaded, but your fetch request only wants those with isSync set to NO. None of those new objects will pass that predicate.*? Thank you in advance.
      singulars
      1. PO
      1. USLorenzo B
    3. CO@AlexsanderAkers Thank you for your comment.
      singulars
      1. PO
      1. USLorenzo B
 

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