Re: Changing value of a WOConditional binding inside WORepetition
Re: Changing value of a WOConditional binding inside WORepetition
- Subject: Re: Changing value of a WOConditional binding inside WORepetition
- From: David Holt <email@hidden>
- Date: Tue, 30 Aug 2005 15:17:01 -0700
On 30 Aug 2005, at 2:49 PM, Chuck Hill wrote:
public void appendToResponse(WOResponse aResponse, WOContext
aContext) {
if (documentToUndelete != null) {
EOEditingContext ec = session().defaultEditingContext();
To make this safer for future changes,
EOEditingContext ec = documentToUndelete.editingContext();
Thanks, I'll do that.
Integer i = new Integer(0);
documentToUndelete.takeValueForKey(i,"deleted");
Why not bury this particular nastiness in the EO where it belongs:
documentToUndelete.undelete();
Okay.
DeletedLookup aDeletedLookup =
(DeletedLookup)documentToUndelete.valueForKey("deletedLookup");
I'm not at all sure what this is.
I'm sure this is a remnant from my SQL days. All I am doing is
providing a description for the 0,1 values in the Document class.
documentToUndelete.addObjectToBothSidesOfRelationshipWithKey(aDeletedL
ookup,"deletedLookup");
Both delete and undelete use
.addObjectToBothSidesOfRelationshipWithKey(aDeletedLookup,"deletedLooku
p"); Should one of them be using removeObject...?
I am just toggling a flag. I included the relationship bit because I
thought it was what was necessary to get the WOConditional to update.
In truth it was all working equally badly by just setting the value of
Document.deleted to 0 or 1.
It is now obvious that there are much better ways to go about this.
What do people normally do to hold pending record deletions? (I would
prefer not to use checkboxes because then I will have to provide the
submit button on the bottom of the form).
_______________________________________________
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