Our data hierarchy has six objects, all of which inherit from "BaseList"
which contains a dictionary (props) and an array (subList). These lists are
chained (i.e., the six subclasses). So in the first-attempt data model,
baselist.sublist is a one-to-many looping back to BaseList.
However, the last item in the chain (Layer) needs it's subList to point
to shapes instead of BaseList, i.e., subList is now a draw list. I could
move subList into the subclasses, but there is a lot of recursive stuff
going on in BaseList where it needs to be. Maybe I could just override an
accessor so BaseList can get to it. Apparently, there's an issue calling
"super" in managed objects, so I'll have to see if that poses any problems.
> On Fri, Jun 6, 2008 at 6:59 PM, Gordon Apple <[EMAIL PROTECTED]> wrote:
>> I'm currently trying to evaluate whether or not Core Data is a viable
>> storage system in our application. Although I've been through the
>> tutorials, Refs, and searches, I still have questions:
>>
>> 1. Our data hierarchy model does not seem to fit into the Core Data object
>> model. (At least I haven't been able to make it fit so far). Now what?
>> Redo the data model?
>
> This seems unlikely. Can you provide some more information on your
> model? You may simply be looking at Core Data the wrong way.
>
_______________________________________________
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
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/archive%40mail-archive.com
This email sent to [EMAIL PROTECTED]
