Re: WO's need to "save changes"
Re: WO's need to "save changes"
- Subject: Re: WO's need to "save changes"
- From: Trae Nickelson <email@hidden>
- Date: Tue, 3 Aug 2004 08:37:33 -0500
Will,
No sweat putting the ec.saveChanges() command (all together with
ec.insert() and everything else) in the same single submit action. I
do it all the time. Works fine for about 90% of the time, when you
don't need a confirmation page or anything. Just remember that you can
use it separately too - comes in pretty handy sometimes.
:-)
Trae
Saving changes on an editing context is something that you usually do
as a developer in some place that makes sense for your application.
perhaps that's why i'm a little confused. for those not familiar with
the sample application I'm referring to, it simply builds a list of
authors and books associated with the authors. There is an "update"
button to update changes you've made to an entry, but the example also
has an explicit "save" button that calls EditingContext.saveChanges().
unless the "save" button is pressed after the "update" button is
pressed, the changes are not committed. so i take it having an
explicit "save" button like this is not normally practiced?... rather
is done behind the scenes at a logic point in the code?
thanks,
will
_______________________________________________
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.