is core data for me?
is core data for me?
- Subject: is core data for me?
- From: "Colm Gallagher" <email@hidden>
- Date: Sun, 23 Nov 2008 20:38:19 +0000
Hi All,
I'm looking to build an address book model, I've happily created many
"fixed" models using core data and they were perfect, I love the "for-free"
stuff that core data brings to the party, it all works fine when I knew in
advance what structure the model took.
I now want to build a model that allows generic addition of columns by the
user (say, adding Shoe Size to the Person entity).
>From a SQL point of view, my approach here would be to build a dictionary
type key-value pair generic model where the person is modelled (in data) as
a list of keys (like shoe-size) and instantiated in values (like size ten).
OK, common enough, easy model to build.
The next step of such a model would be to query that model and it's this
point at which I fall down Hard. I can only seem to work with the data in
it's abstract form, I can't find any way to natively recombine my data using
the equivalent of an SQL query - due exclusively to the seeming lack of any
kind of Joins between entities (except for the "quick lookup" provided by
fetched properties).
Am I expecting too much? Is core data simply unsuitable for such an
approach to modelling? I'm currently investigating just doing it all myself
an using sqlite or one of it's many wrappers, but before I go down that
road, I thought I'd ask for help, maybe I'm missing something.
ps - adding (userConfigAttribute1, userConfigAttribute2, etc. to a person
entity is an option I've already discarded)
thanks
--
Colm
_______________________________________________
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