Re: Multiple Self-joins
Re: Multiple Self-joins
- Subject: Re: Multiple Self-joins
- From: Chuck Hill <email@hidden>
- Date: Wed, 12 Jan 2005 11:55:29 -0800
On Jan 12, 2005, at 11:49 AM, David Holt wrote:
Hi Chuck,
I can create a to-one relationship (named parentImage) and a to-many
relationship (named childrenImages) linked on the primary key of the
image table.
Linked to what?
When I go to create an additional to-one relationship (nextImage or
previousImage),
Linking what to what?
the inspector in EOModeler shows the entities as already being
connected by their primary keys and the button is labelled
"disconnect". There is no way to create additional relationships using
the same primary keys without disconnecting the previous relationship
as far as I can tell.
Of course not. The same thing can't be different things at the same
time. Draw it out on a piece of paper. You need
pk
parentFK (PK value, but a FK in use) -> for parentImage, childImages
previousFK -> for previousImage
nextFK -> for nextImage
You might want to forget about the previousFK and nextFK and just use
an order column and make previous and next image methods on the parent.
It will be a lot easier to reorder like that.
Chuck
On 12 Jan 2005, at 11:41 AM, Chuck Hill wrote:
Um, do we get to know what it complains about?
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
village.net
This email sent to email@hidden
--
Practical WebObjects - a book for intermediate WebObjects developers
who want to increase their overall knowledge of WebObjects, or those
who are trying to solve specific application development problems.
http://www.global-village.net/products/practical_webobjects
_______________________________________________
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