The basic fact is that an array is an array and a set is a set Sure,
the implementation could vary, depending on performance constraints. What
he (and others) have asked for is any solution (or reference to a solution).
A lot of us would like to see it. I haven't tackled core data or BigTen
yet, so I don't know what is involved. I just know I'm going to have to
crack that nut sometime soon. Fortunately, my current stuff is mostly in
the small array ( <100 ) category.
> Actually this is probably not the case. The difficulty (as I
> understand it) is that while there are many, many people who want to
> have ordered collections in their databases, each program has subtle
> differences in it's requirements that make this a difficult problem to
> solve in a generic fashion. For example, my application likes to
> order small groups of objects (say 20 at the most) while another
> program might need to order 100,000 objects. Each of these two
> applications might use a different strategy.
>
_______________________________________________
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:
http://lists.apple.com/mailman/options/cocoa-dev/email@hidden
This email sent to email@hidden
