Skipping the need to back out with saves in D2W?
Skipping the need to back out with saves in D2W?
- Subject: Skipping the need to back out with saves in D2W?
- From: Ashley Aitken <email@hidden>
- Date: Mon, 19 Apr 2004 00:06:04 +0800
Howdy All,
Within the D2W standard paradigm there seems to be a strong emphasis on
sequences like:
Edit Item -> Edit SubItem -> Edit SubSubItem
Requiring sequences like:
Save SubSubItem -> Save SubItem -> Save Item
To back out and make sure all the changes get to the database.
I understand why this is so conceptually (if you don't actually Save an
Item t is the Save to the SubSubItem supposed to be saved?) and
technically (a lot of these edits, I believe, are done in nested
editing contexts and require the additonal saveChange to get the
changes back to the database).
My question is:
Is there are general way (apart from counting nestings and doing
multiple saveChanges yourself, if it is possible to climb the
editingContext hierarchy like that) to make a save recurse all the way
up to the database (or datasource).
My client wants:
Edit Project -> Edit Job -> Edit Item
To allow ONE Save, something like: saveAllChanges() or
saveToDataSource() or ...?
I've CC'ed this to Project WONDER just in case they have any neat magic
in their frameworks to do this.
Thanks in advance,
Ashley.
--
Ashley Aitken
Perth, Western Australia
mrhatken at mac dot com
_______________________________________________
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.