Re: Core Data Abstractions
Re: Core Data Abstractions
- Subject: Re: Core Data Abstractions
- From: T Reaves <email@hidden>
- Date: Mon, 30 May 2005 21:37:20 -0400
On May 30, 2005, at 6:43 PM, mmalcolm crawford wrote:
On May 30, 2005, at 3:35 PM, T Reaves wrote:
On May 30, 2005, at 2:02 PM, mmalcolm crawford wrote:
The analogue here would be to create another entity to which all
the Projects are related. You then "fetch" the Projects simply
by following the relationship.
Whereas this would work, it's a nasty hack just to retrieve an
extent (all instances of a particular class). Wanting a class
extent is a fairly common thing, and needing to create and manage
collections manually to help is tedious at best.
(a) It's a perfectly respectable design pattern, not a "nasty hack".
(b) The whole point is to not have to create and manage collections
manually -- you simly use the relationship.
Well then perhaps I misunderstand your solution. I thought you
were saying to create an entity with a to-many relationship to
another entity. Then, on the first entity, you could call
myCollection, or whatever named accessor. This would certainly be a
nasty hack (adding objects to an application not for business
reasons, but ill-fitting implementation reasons), and would require
adding instances of the second entity to the collection of the first
entity, wether by explicit adding or via a factory method would be
irrelevant.
Because you state it is neither of the two things I've just
outlined, I'm not sure what you meant. Would you please explain a
little more?
_______________________________________________
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