Re: Can't modify EO objects! ARGH! =(
Re: Can't modify EO objects! ARGH! =(
- Subject: Re: Can't modify EO objects! ARGH! =(
- From: Arturo Pérez <email@hidden>
- Date: Thu, 17 Jul 2003 22:42:23 -0400
On Thursday, July 17, 2003, at 07:11 PM, Art Isbell wrote:
On Thursday, July 17, 2003, at 11:59 AM, Albert Jagnow wrote:
I am confused by the pattern you list below. I have had more problems
doing insert before populate.
As Chuck stated, these problems can be dealt with by making the
changes in an editing context whose parent is the session's default
editing context. If you decide not to save these changes, set this
editing context to null so it is garbage collected. The session's
default editing context won't realize any changes have been made.
If you do decide to save the changes, send a saveChanges() message to
the nested editing context which moves the changes up to the session's
default editing context. If this parent is the session's default
editing context, then send a saveChanges() message to it to save to
the DB.
Another possibly less flexible approach is to use just the default
editing context. If you make changes that you don't want to save,
send the editing context a revert() message.
How does the undoManager affect the above explanation?
-------
WebObjects in Philadelphia. You want a cheesesteak with that?
_______________________________________________
webobjects-dev mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/webobjects-dev
Do not post admin requests to the list. They will be ignored.