Re: WO's need to "save changes"
Re: WO's need to "save changes"
- Subject: Re: WO's need to "save changes"
- From: steve stout <email@hidden>
- Date: Mon, 2 Aug 2004 17:15:18 -0700
Exactly. You can use the ability to update the values of an EO and
then later save them to the database to give the user a way to view any
pending changes before it's actually saved to the db, or allow them to
make multiple changes and save it all at once. But most of the time
you'll want to make that distinction a little more user friendly, as in
the case of the shopping cart. If you really want them to save
something right away, then make the saveChanges part of your action
method.
.steve
On Aug 2, 2004, at 5: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?
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.