Re: How do I update a relationship in a WODisplayGroup?

Tue, 13 Dec 2005 13:52:31 -0800

Hi Ken,

Thanks for the tip.  

You were correct, I was doing some iterative development and was cheating by changing the code itself while I figured out how to create and properly bind a WOPopupButton.  While waiting for a reply, I figured out how to add the WOPopup Button (drop down list) and low and behold, it works.  Now when I change the selection of the dateFormatList WOPopup button and hit my submit button, it saves both in the database and refreshed my WODisplayGroup properly.  (I even removed the invalidateAllObjects()).  Less code and makes sense.

After reading you response, I continued to examine my EOModel and found that dateOfBirthCode was a class property.  I removed it and all still works.  It makes sense that I confused EOF with multiple editing points.

I will learn to let EOF do the heavy lifting :-)

Thanks again,

Kev


On 13 Dec, 2005, at 04:19 PM, Ken Anderson wrote:

Is the dateOfBirthFormatCode a class property?  If it is the basis for a relationship, it shouldn't be.  You should let EOF take care of the keys, and change the relationship to the new format, rather than changing the code itself.

In general, attributes used to define relationships should not be class properties - it understandably confuses EOF if there are effectively 2 different ways to change a relationship.

In case you don't know, the diamond symbol denotes a class property.

Ken

On Dec 13, 2005, at 3:57 PM, [EMAIL PROTECTED] wrote:

Hi all,

I have been following Nathan's WODisplayGroup podcast and incorporating some of his ideas into my own application.

I have a simple WODisplayGroup that displays a group of Localizations.  (Localization is the entity).  This entity has single to-one relation to another entity called DateFormatCode.

Localization
----------------
code
descriptor
primaryIdDescriptor
primaryIdFormat
dateOfBirthFormatCode   (-> to-one relationship to DateFormatCode.code)

DateFormatCode
-----------------------
code
displayedDateFormatString
javaDateFormatString

From EOModeler I have set up the relationship and created a simple WODisplayGroup on a WOComponent that has a WOForm that accepts edits to the Localization entity and saves them to the database.  The WODisplayGroup is set to "Fetches On Load".

All seems to be working great.  I can change any of the attributes of the Localization entity (such as descriptor, primaryIDFormat, etc).   When I change any of these attribute, I immediately see the changes reflected in the WODisplayGroup.   However, while I can change the dateOfBirthFormatCode, and I even verify it is stored in the database, my WODisplayGroup still shows the old value.  (I am actually displaying the displayedDateFormatString attribute by walking the relationship).  If I restart the application, then and only then, does the related item reflect the last change.

I have tried to use redisplay() and fetch() on the WODisplayGroup  before returning the page, but it did not have any affect.  I have searched the lists and found one other who asked a similar question.  He eventually answered himself after getting no responses and stating that he used invalidateAllObjects() on his editing context.  I tried this as well and it works, but I share his concern that I feel guilty with having to do this.  It seems like overkill to me.  

Any suggestions?

Thanks,

Kev
 _______________________________________________
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