Re: Core Data performance advice... creating relationships.
Re: Core Data performance advice... creating relationships.
- Subject: Re: Core Data performance advice... creating relationships.
- From: Martin Linklater <email@hidden>
- Date: Tue, 15 Jan 2008 01:37:40 -0800
On Tuesday, January 15, 2008, at 09:15AM, "Phil" <email@hidden> wrote:
>Could you elaborate on why you changed your position? In reading your
>initial reply, I was inclined to agree that Core Data probably wasn't
>the best solution in this instance (i.e. it's a decent-sized data set
>and what was being described appeared to be a simple table join
>scenario with no clear OO requirements.) What did you see in the
>original post that caused you to believe that, in fact, this really
>was a Core Data usage scenario? Understanding your thinking might
>help people like myself who are still struggling with where to draw
>the line on using Core Data vs. a relational approach.
I can't see why Core Data would not be applicable in this instance. My code basically parses a load of SQL table create commands and recreates the data within Core Data. Since Core Data supports an SQLite backing store I don't see why data size of amount of relational information would factor... My plan is also to leverage Bindings and Core Data to simplify my UI code. Core Data's ability to deal with complex fetch predicates is also a win for me since I can let Core Data do a lot of the heavy lifting within my dataset.
In fact the only downside I can see of using Core Data over a 'proper' relational database is that Core Data fetch requests return the entire entity rather than specific entity attirbutes, but since I'm only dealing with a single user application and relatively small objects I can't see this minor performance problem being an issue at all. Once my backing store is created I'm only really going to be accessing it in a read-only manner. My plan is to store all dynamically created user data in a separate object model, so as to keep my data relationships as simple as possible.
Core Data seems like the perfect fit for me. Plus it's a good learning exercise 8).
I must add the caveat that I'm in no regard a 'Databse Programmer', so my opinions may be pretty naive about this...
Thanks.
_______________________________________________
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