Re: Core Data SQL store looses data that XML store does not
Re: Core Data SQL store looses data that XML store does not
- Subject: Re: Core Data SQL store looses data that XML store does not
- From: mmalcolm crawford <email@hidden>
- Date: Wed, 10 Aug 2005 17:37:25 -0700
On Aug 10, 2005, at 12:08 PM, Scott Ellsworth wrote:
I believe I was led astray by "It is possible, however, for
relationships to be navigable in only one direction—for there to be
no inverse relationship. If, for example, you are never interested
in finding out from a department object what employees are
associated with it, then you do not have to model that
relationship." from the data modelling guide.
The Data Modeling Guide is not specific to Core Data (it also
presents information relevant to Cocoa bindings). From the "Inverse
Relationships" section of the Core Data Programming Guide: <http://
developer.apple.com/documentation/Cocoa/Conceptual/CoreData/Articles/
cdRelationships.html#//apple_ref/doc/uid/TP40001857/
DontLinkElementID_21>
"It is not strictly necessary to model a relationship in both
directions. In some cases it may be useful not to, for example when a
to-many relationship may have a very large number of destination
objects and you are rarely likely to traverse the relationship (you
may want to ensure that you do not unnecessarily fault in a large
number of objects at the destination of a relationship). *If you do
not, however, you may need to do additional work to ensure the
consistency of the object graph. It typically only makes sense to
model a to-one relationship in one direction.*"
mmalc
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden