iphone - fetchedresultscontroller with two entities - predicate to target each entity? -

There is a summary page in my iPhone app (UITTVview) where I have to show a quick overview and so I need to get the information It was suggested for many institutions to make this an abstract original unit and for my two organizations in the form of children of this one. This allows me to bring two entities using a fetchedresultscontroller.

This works but I think I have to filter a little bit. There is nothing in common due to 'hack' above these institutions so I need a completely different future. So with Antita, I would need "color = blue" and "entityb" length = 10 = "". Because whatever I really ask is none of these, it does not work at all.

Is there any way to do this or what is the best way here?

Neether Uitable Weave or NSFED Result Controller designed to deal with more than one unit at a time is. Apart from this, it rarely makes any sense to try to do this. If you find yourself in such a situation, then you probably need to think about your data model design again.

If the institutions are related to each other logically then they should be linked to the relationship. If any data from any two objects is going to appear in the same table view then they should have some rational support to be without any liability and therefore should be related to some kind of relationship. To display in the table, you take one side of the relationship and then move the relationship to find other related objects.

If the logical union is strong, then it should be defined as the formal relationship of data models such as:

  EntityA {// ... some features b & lt ; - & gt; EntityB {//..some attributes a & lt; - & gt; Ab}   
 However, if the relationship is weak or transient, then you should use them to relate. Receiving property dynamically searches for other organizations based on a preprogrammed fetch.  
  EntityA {creationDate: date someBs - (creationDate = $ FETCH_SOURCE.creationDate) - & gt; B} EntityB {creationDate: date}   
 A key concept is that core data is providing the complete model layer of your model-view-controller design. This is not just a dumb database but an active object graph, which does both the data and the behavior of the self. Once you have a properly designed data model, problems with controllers and ideas are automatically resolved.