Are you using subclassing? If two entities that subclass the same
parent class have an identical relationship to another entity, that
relationship should be defined in the abstract parent class. In
addititon, there should only be a SINGLE inverse relationship from
the target entity, pointing back to the abstract superclass. If you
define two inverse relationships, setting both sides of the
relationship will tend to not work.
Also, make sure that any keys used in your relationship are not class
properties. In my experience this can prevent them from being set
correctly.
--
Sam Barnum
360 Works
http://www.360works.com
415.865.0952
On Oct 18, 2007, at 8:47 PM, Owen McKerrow wrote:
Further information....
When I try and print out the revrse relationship from AuthorPub
back to Person I get null. i.e. EOF can't find the reverse
relationship back to the Person from the join.
log.debug("The relationship going back the other way is ...." +
tempRec.inverseForRelationshipKey(relationshipName));
give us
The relationship going back the other way is ....null
Which to me means I don't have the relationships inside EOModel set
up correctly ?? What are other peoples take on this ?
Owen McKerrow
WebMaster, emlab
Ph : +61 02 4221 5517
http://emlab.uow.edu.au
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- - - - - - - - - -
'The test of a first-rate intelligence is the ability to hold two
opposed ideas in the mind at the same time and still be able to
function.'
-F.Scott Fitzgerald,
On 19/10/2007, at 12:04 PM, Owen McKerrow wrote:
Hi Lachlan,
Nope that didn't fix it either :(
Owen McKerrow
WebMaster, emlab
Ph : +61 02 4221 5517
http://emlab.uow.edu.au
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- - - - - - - - - - -
'The test of a first-rate intelligence is the ability to hold
two opposed ideas in the mind at the same time and still be able
to function.'
-F.Scott Fitzgerald,
On 19/10/2007, at 11:36 AM, Lachlan Deck wrote:
Hi Owen,
On 19/10/2007, at 11:24 AM, Owen McKerrow wrote:
Im having a problem with
addObjectToBothSidesOfRelationshipWithKey, either that or I
don't understand how its meant to work correctly. That is when
you use addObjectToBothSidesOfRelationshipWithKey the
relationships between both objects should be updated. So if you
have a relationship between a dog and a cat, when you use
addObjectToBothSidesOfRelationshipWithKey to set the dog's
relationship to cat, its should auto set the cat's relationship
back to the dog.
Try the ol' removeObjectFromBothSidesForKey on objects you're re-
pointing elsewhere.
with regards,
--
Lachlan Deck
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list ([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/owen%
40uow.edu.au
This email sent to [EMAIL PROTECTED]
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list ([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/sam%
40360works.com
This email sent to [EMAIL PROTECTED]
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list ([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com
This email sent to [EMAIL PROTECTED]
