title: Should I Use a FetchedResultsController for Objects in a Constantly Updating Relationship?
body: <p>I have a simple Coredata model with one entity called "conversation" and the other one "messages". Basically, I need to kind of reproduce the iPhone sms application. </p>
  
  <p>I have a to-one relationship  from message to conversation and a to-many from conversation to messages.</p>
  
  <pre><code>Conversation{
      messages&lt;--&gt;&gt;Message.conversation
  }
  
  Message{
      conversation&lt;&lt;--&gt;Conversation.messages
  }
  </code></pre>
  
  <p>Anytime I launch my app, all my conversation are loaded in my fetchedResultsController. If I understood correctly how Coredata works, as I have a relationship, every messages linked to my conversation will be loaded as well right? I set up a batch size so that I don't load all my conversations at the same time.</p>
  
  <p>My app is connected to a server via a long pulling request, so I can receive an message from the server at any time (there will be added to coredata and then I use NSNotification to tell my views something append).</p>
  
  <p>MY problem is this: When I select a row, I push another view on the stack, so that I can see my messages. I was wondering how to do that, and there is why: </p>
  
  <p>• I could pass to my view my NSSet of messages given via the relationship, right? however, as I can receive a message, while looking at that view, how do i refresh the NSSet passed to the view?</p>
  
  <p>• I could also use another fetchedresultController in that view, but in that case, I would be pre-loading all my messages in my previous view for no reason ? Can I tell coredata not to load them in my previous view?</p>
  
  <p>I hope this was clear enough. I kind of desperate and I know there are some expert on that website. Let me know if you need anything else, I'll try to provide more information as soon as possible.</p>