Re: WO's need to "save changes"
Re: WO's need to "save changes"
- Subject: Re: WO's need to "save changes"
- From: David LeBer <email@hidden>
- Date: Mon, 2 Aug 2004 20:19:08 -0400
On 2-Aug-04, at 8:05 PM, William Norris wrote:
On Mon, 2 Aug 2004 16:55:53 -0700, steve stout
<email@hidden> wrote:
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?
I think that example is demonstrating that the two functions (updating
and saving) are not necessarily the same thing and can easily be
treated separately.
For example:
An admin app may always save during a submit.
A wizard driven process (shopping cart etc.) may save only once at the
end. The preceding steps are just updating the in memory data.
;david
--
David LeBer
Codebase Software Systems
site: http://www.codebase.ca
blog: http://david.codebase.ca
_______________________________________________
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.