On Mon, Nov 24, 2008 at 6:23 AM, Paul Tomlin <[EMAIL PROTECTED]> wrote:
>
>
> I would create a separate Entity in your model and then define a to-many
> relationship from your "Person" to that new Entity, possibly called
> something like "PersonAttribute". The new Entity may have, for example,
> At
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 t