In my Core Data data model, I have four different entities, each of which implement a lookup list. That is, the entity has one attribute (a name string) and a relationship pointing to all of the other objects which use that particular term.
I am considering two different ways of implementing these lookup lists - either as four separate (and independent) entities or as a single entity (with an additional attribute which is the lookup-list-type). Which approach is better and why do you think so? On the one hand, I can see advantages to having one lookup-list entity in the data model vs. four, both in terms of the complexity of the data model and in storage efficiency. On the other hand, while the extra coding cost of a single list is modest (a slightly more complicated predicate, since I always have to specify the list-type attribute in any fetch request), there are bound to be some increased processing costs. What are your experiences? Cheers, Rick Aurbach Aurbach & Associates, Inc. _______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
