Re: Core Data using only one object
Re: Core Data using only one object
- Subject: Re: Core Data using only one object
- From: John Stiles <email@hidden>
- Date: Tue, 24 Apr 2007 17:43:20 -0700
On Apr 24, 2007, at 5:10 PM, mmalc crawford wrote:
On Apr 24, 2007, at 4:57 PM, Steve Israelson wrote:
Very funny.
Google: coredata elaborate site:developer.apple.com
returns 0 results.
It's not clear why this is of relevance?
The technology name is "Core Data", not "coredata", and there is no
reason to suppose that "elaborate" would be a useful term for which
to search when looking for a definition.
I suppose I meant explicitly stated.
When learning about any technology, a good place to start is with
the related Programming Guide.
The very first sentence of the Introduction to the Guide begins:
"The Core Data framework provides generalized and automated
solutions to common tasks associated with object life-cycle and
object graph management..."
which is effectively a superset of:
"The point of Core Data is to make it easy to work with elaborate
object graphs."
Honestly, I see where you're coming from, but I also see the OP's
point that it really isn't stated anywhere. The Core Data docs speak
in some high-falutin' language sometimes, and this can definitely
cloud over the actual meaning. And in all fairness, the actual
sentence in the docs says nothing about the complexity or
elaborateness of the graphs. Perhaps Core Data could make my life
easier when dealing with a graph of three nodes—why not? The docs
don't make an attempt to discourage this line of thinking. Perhaps
you are confusing what you know for sure, and what is written down.
_______________________________________________
Cocoa-dev mailing list (email@hidden)
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:
This email sent to email@hidden