Help with Multiple FetchResultsControllers (Core Data)

[Nekbeth]

Hi, I added navigation based category tableview, after I select the cell it takes you to another Controller who has specific entity descriptions and predicates on it's FetchResultController, the results is working fine, but only for the description of the fetchresult.. (which in this case is by a attribute that contains a strings).

What I want to do next is to select a different cell (with a different strings obviously) and give me a similar result to the one above. My way to do this (may not be the best).. is to:

1- Make another viewcontroller with it's tableview
2- Create another FetchresultsController inside it (with it's particular description on the predicate)
3 - Just push that controller when the cell is selected.



Is this the right way ? create a new viewController for each FetchResultsController? or can I create FetchresultsController instances in 1 viewController only .. I don't think I can.. but I wanted to be sure. If there is another way to get this results, I'll appreciate your ideas.

Again, what I want is to select a category I choosed before from an entity. A tableview appears with only the categories of that entities, when you select a category .. it should give you the "names" attribute of those entities.
So I have that working ok, if I select only 1 category (for instance Chocolate and it pushes me to all chocolate cakes). I want to do the same thing with Cheese, so it gives me all the Cheese cakes. This could mean making a lot of viewControllers (for each FetchResultsController). So that is my doubt.

Thanks

[dljeffery]

The normal way, assuming that your data is all structured similarly (and it sounds like yours is), is to always push the same secondary view controller from your table view controller. Just pass in the data needed to initialize the secondary view controller properly.

Especially in the case you describe, if in view 1 you tap on "Chocolate", you just push a second view with a list of all the chocolate cakes, right? And if you tap on "Cheese" instead, you push a second view with a list of all the cheesecakes? And then, I assume, from the secondary view, if you type on a name of a specific cake, you push a third view that shows the recipe, perhaps a photo, etc. If so, you definitely don't want custom views for each type. And if you did have custom views for each type, that would mean that you can't dynamically define new types at runtime.

Perhaps I'm not reading your description clearly, though.