Re: CORE DATA: derived values from several entities and managed object instances ??
Re: CORE DATA: derived values from several entities and managed object instances ??
- Subject: Re: CORE DATA: derived values from several entities and managed object instances ??
- From: dan pahlajani <email@hidden>
- Date: Wed, 25 Jan 2006 10:31:20 -0800
You do have a point. If efficiency is not important your suggestion
would definitely work. I appolgize. I am just frustrated. Core Data
is such a well design framework, but in my opinion with some
serious limitations, like before an object is saved allow me to update
certain values which any real world application would need to.
Anyway, I won't list all the limitations here.
All I would want is a way to ask Core Data to return me an
ordered collection which it already seems to have loaded,
then I can go about doing my calculations.
Again, I appologize for showing my frsutratin.
--Dan
On 1/25/06, I. Savant <email@hidden> wrote:
>
> Dan:
>
> I was the one who made the 'silly suggestion'. As I recall, there
> wasn't sufficient information in your previous post to infer what
> you're trying to do. For most desktop apps, however, a sort order key
> or even a linked-list approach is about all you've got for ordered
> lists with Core Data and will work just fine with relatively small
> data sets.
>
> If you have hundreds of calculations taking place on hundreds of
> objects, obviously neither approach will be the most efficient way of
> doing things. I made no such claim in my previous post.
>
> In any case, I don't understand enough about what you're trying to
> do to give a better suggestion. If it doesn't work for you, fair
> enough. I just felt compelled to defend my silly suggestion ...
>
> --
> I.S.
>
>
> On Jan 25, 2006, at 12:18 AM, dan pahlajani wrote:
>
> > Someone on the Cocoa List responded to my question by saying, I could
> > set a "sortOrder" and do a fetch to receive"ordered" object set. I
> > think it is a sily solution. Why do I perform so many fetches (since
> > the there could be hundreds of calculations taking place involving
> > hundreds of objects) - it is absolutely inefficient especially when
> > all the objects are already there either owned by Core Data or by
> > Array and Tree Controllers. I understand the concept of uniquing but
> > still it seems inefficient to me.
>
>
_______________________________________________
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