On Feb 5, 2011, at 3:08 PM, James Cicenia wrote: I think the relationship was wrong... I regenerated it and then it worked.
thanks
I have had this problem. I griped about it in a thread within the last year or so. I had the propagate primary key set weirdly and the WOLips tools did not respond to my off-kilter suggestions.
I find that once I make sure the intermediate relationships are not class properties and set the propagate primary key to both joins and set the deletion policy correctly, things always end up working. I think Mike told me to just do the setup in the normal way and get over myself with my weird setup.
The validation warnings from the tools are not very smart about many-to-many relationships, or so it seems to me.
- ray
On Feb 5, 2011, at 4:42 PM, James Cicenia wrote: The list is using localInstanceOfObjects
James
On Feb 5, 2011, at 4:36 PM, Paul D Yu wrote: Are they in the same editingContext?
Paul On Feb 5, 2011, at 5:27 PM, James Cicenia wrote: Here is the error:
A valid global ID could not be obtained for entity named PortfolioProjectPortfolioProject, relationship named childProjects, primary key dictionary {childProjectRowId = 69063; }
The project with that row id (69063) does exist and would be the correct one.WOBrowser: childProjects: WOBrowser { displayString = aChildProject.title; item = aChildProject; list = possibleChildProjects; selections = theNewProjectItem.childProjects; multiple = true; }
theNewProjectItem.childProjects is the "flattened relationship".
What am I missing here? Thanks James Cicenia
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden
|