Re: "Saving" changes to an object's variable(s) but not save changes to database.

one option is create an editing context for the session, apply your  
changes in the normal EOF way, just don't call saveChanges.
Subsequent requests grab that editing context from the session and  
see the changes that have been made.   Does that help?

Alan

On Aug 29, 2006, at 8:54 PM, Tony Hoffman wrote:

> I have what may be such a profoundly stupid question that it may  
> need to be ignored by all. I've gone through my books and the list  
> and Google searches and I still can't find anything that gets me  
> even close to the answer (also usually a big tip off that my  
> question/and or thinking is deeply misguided).
>
> My problem is basically this: I want users of my web application to  
> be able to make form input changes into the variable value of each  
> instance of an object generated from an EOFetchspecification. And  
> then I want to be able to save these values in the session so that  
> I can move it between components, refer to it, and then have it  
> disappear at the end of the session without ever bothering the  
> database again. If I were to use the saveChanges method on the  
> editingcontext for this NSMutableArray of objects and its input  
> variables, everything works fine, but I don't want to save changes  
> to the database, I want to save changes to the (temporary) values  
> in the variable in the objects held in the session.
>
> I have the WOTextFields just sitting there. All I want to do is  
> link them up with some kind of action method that will record the  
> user input into the object variables in the session WITHOUT saving  
> those changes to the database. It seems so basic that I have to  
> ask, what am I missing?
> _______________________________________________
> WebObjects-dev mailing list
> [email protected]
> http://www.omnigroup.com/mailman/listinfo/webobjects-dev