Re: Attempt to insert null key into a com.webobjects.foundation.NSMutableDictionary
Re: Attempt to insert null key into a com.webobjects.foundation.NSMutableDictionary
- Subject: Re: Attempt to insert null key into a com.webobjects.foundation.NSMutableDictionary
- From: Art Isbell <email@hidden>
- Date: Wed, 14 May 2003 12:18:33 -1000
On Wednesday, May 14, 2003, at 11:58 AM, Jevon Hills wrote:
Sorry Art, I'm still learning. What do you mean 'underlying
relationships of a flattened relationship are class properties'?
A flattened relationship spans an entity that's related to the source
and destination entities of the flattened relationship. If you look at
the definition of the flattened relationship, you'll see that it's
comprised of a couple of relationships. These relationships shouldn't
be class properties.
I have two tables joined by a 'link table' , I flattened the
relationship in eomodeler by selecting the CollectionDesc entity, them
the relationship to Collection (the link) and then the relationship to
Content and flattened on that so that now my CollectionDesc has
methods to set/get Content objs.
Have I done that part correctly??
Possibly not. You should allow EOModeler to create this many-to-many
relationship for you. Select the model entry at the top of the
entities list in the left pane of EOModeler. In the right page will be
the list of entities in the model. Command-select (or if Windows, do
whatever supports multiple selections) the CollectionDesc and Content
entities. In EOModeler's menu, click "Join in Many to Many" (not sure
of the exact wording). This will create the join entity,
CollectionDescContent, and all of the necessary relationships. But
you'll notice that CollectionDesc.collectionDescContents and
Content.collectionDescContents are not class properties. If you need
to follow these relationships in your app to access
CollectionDescContent, then you'll have to delete the flattened
relationship and make these relationship class properties because the
flattened and underlying relationships can't all be class properties.
You'll probably want to replace the Collection entity with
CollectionDescContent.
Aloha,
Art
_______________________________________________
webobjects-dev mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/webobjects-dev
Do not post admin requests to the list. They will be ignored.