Re: A Bad Bug?

Tue, 19 Sep 2006 10:39:47 -0700

Yes, it is a plain standard EOModeler two-way relationship   CTCampaign <<--> CTMediaTemplate. Both are abstract classes .... don't know if that makes a difference.

Here is my tech specs. The problem manifested itself both on DEV and DEPLOYMENT with the same behaviour.
Dev Config = OS X 10.4.6 i686-C.Duo / Java 1.4.2_09 /  WO 5.3.1 & P. Wonder / XCode v2.2.1 / MySQL 4.1.18-std / Connector-J 3.0.17
Deploy Config = OS X 10.3.9 Server G4-PPC / Java 1.4.2_09 / WO 5.2.3 / MySQL 4.0.26 / Connector-J 3.0.17

Regards, Kieran

On Sep 19, 2006, at 1:02 PM, Ken Anderson wrote:

Does the target of the relationship have a reciprocal relationship?  If so, this would explain the problem, since EOF wouldn't know which way you wanted the relationship (you created an inconsistency in the data).

Ken

On Sep 19, 2006, at 12:24 PM, Kieran Kelleher wrote:

Here is one that bit me bad yesterday. I am trying to understand if it is really a bug situation or not, or whether the code I used is expected to produce unpredictable behavior like this did.

I was using eoSourceObject.takeValueForKey( destObject, relationshipKey ) to set a relationship. Upon saving the eoSourceObject had the corrected related object and the editing context state was correct with the relationship made, etc. I could navigate the EC and objects in the EC using the DebugMarker and ec examination pages in Project Wonder. SO basically as far as the EOF was concerned, all changes had been saved and the current state of the EC reflected the current state of the database. 

However the foreign key was actually not getting updated in the eoSourceObject table. Logging SQL showed that indeed this was the case. The source object was written out to the database with the old foreign key even though the ec had the new related object!

Now digging a little deeper, the takeValueForKey was calling the auto-eogenerated code which in turn called takeStoredValueForKey (CTMediaTemplate is the destination object here and this method is in the eogenerated _CTCampaign, the source object.)
    public void setMediaTemplate(CTMediaTemplate aValue) {
        if( log.isDebugEnabled() ) log.debug( "updating mediaTemplate from "+mediaTemplate()+" to "+aValue );
        takeStoredValueForKey(aValue, "mediaTemplate");
    }

At face value, it seemed like everything was fine and confirmation pages of the saved state of the EC showed everything OK ..... but later once the snapshot expired, the snapshot got updated form the database and the OLD original foreign key showed up and then the wrong related destObject was displayed ..... AAARRRGGGHHH!!!

The SOLUTION was to change my code to use
eoSourceObject.addObjectToBothSidesOfRelationshipWithKey( destObject, relationshipKey);

.....but WHY does not takeValueForKey or takeStoredValueForKey not set the relationship both ways?

Kieran


 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list      ([email protected])
Help/Unsubscribe/Update your Subscription:

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]

Reply via email to