Good morning, I am trying to figure out the best way to model a Core Data relationship.
Essentially, I am trying to have an "Address" object that can be referenced by "Contacts" and "Companies." In other words, contact entities should have multiple addresses (one to many), and company entities should have multiple addresses as well. However... when I do a unidirectional one to many relationship, the compiler (rightly) complains as I do not have inverse relationships. However, it makes no sense to me to clutter up my address object with pointers back to "company" and "contact" and perhaps any other entity down the line that may need an "address." Anybody solved this one and have some advice? Is this a place for a "fetched property?" Thanks in advance, Best Regards, Mark Smith _______________________________________________ Cocoa-dev mailing list ([email protected]) 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: http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to [email protected]
