Re: Core Data performance advice... creating relationships.
Re: Core Data performance advice... creating relationships.
- Subject: Re: Core Data performance advice... creating relationships.
- From: mmalc crawford <email@hidden>
- Date: Tue, 15 Jan 2008 08:32:10 -0800
Briefly for now...
On Jan 15, 2008, at 3:46 AM, Phil wrote:
You appear to be describing a traditional SQL database application
(your latest post with the schema seems to confirm it.) The first
half of what you wrote has me thinking 'probably not a great
application for Core Data.' The second half re: UI makes sense if
you understand the overhead you are going to incur and that the
benefits provided are worth it. Core Data is not just an OO wrapper
to a relational database. It uses SQLite as a persistent object
store but don't be fooled into thinking that this is the same thing.
I don't believe he is, and I.S. has already made the point that it's
an object-graph management and persistence framework. If in your
application you leverage that feature, it probably is a good fit.
There is much more to it than that as you are throwing a lot of work
'over the wall' to Core Data which has a non-trivial cost in terms
of performance and memory.
It's not clear on what basis you make this assertion.
Similar caveat on my end: I have quite a bit of experience in the
relational database world but am still learning Core Data. (hence
my original question... so I'd appreciate enlightenment on where I'm
off-base in this reply.)
See <http://developer.apple.com/documentation/Cocoa/Conceptual/CoreData/Articles/cdFAQ.html#//apple_ref/doc/uid/TP40001802-DontLinkElementID_27
>
mmalc
_______________________________________________
Cocoa-dev mailing list (email@hidden)
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:
This email sent to email@hidden