Re: CoreData Best Practices
Re: CoreData Best Practices
- Subject: Re: CoreData Best Practices
- From: John Timmer <email@hidden>
- Date: Fri, 29 Apr 2005 19:13:11 -0400
> On Apr 29, 2005, at 3:29 PM, John Timmer wrote:
>> Stick an order key in every author, and use that to sort an array
>> created
>> out of the set. This seems better, but commits you to having a unique
>> author instance for every place an author appears.
>
> It sounds like you need this anyway since earlier in your post you said
> there are essentially no ways of identifying when two authors are
> identical.
>
> -- Chris
Well, as I said there, you can match author's names. You wouldn't match
Hanson, C with Hanson, Chris even if they were the same person, but you
could match all instances of Hanson, C. Even if they weren't the same
person, they'd be indistinguishable at this level.
I did say that I'm not sure where that would come down on the
performance/memory use equation, though. I haven't done a multi-way search
on a managed object context with > 10000 objects yet. Anyone know how quick
that is?
JT
_______________________________________________
This mind intentionally left blank
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden