Re: ERXEC.newEditingContext() instead of the defaultEditingContext()
Re: ERXEC.newEditingContext() instead of the defaultEditingContext()
- Subject: Re: ERXEC.newEditingContext() instead of the defaultEditingContext()
- From: Guido Neitzer <email@hidden>
- Date: Mon, 15 Sep 2008 11:05:43 -0600
On 15.09.2008, at 10:34, Theodore Petrosky wrote:
I have used the ERXEC.newEditingContext() to access my database.
but is another component I need to save my changes... so the
defaultEditingContext doesn't help.
If I assess my data like this:
fetchResult = Order.fetchIsNotCompleted(ERXEC.newEditingContext());
I can not use:
session().defaultEditingContext().saveChanges();
I have googled and googled and can not find an answer.... sorry for
the completely newbie(ized) question.
You always save the editingContext of the objects you want to save. In
the examples that is often the defaultEditingContext but it doesn't
have to be.
If you have any EO, you can always call:
object.editingContext().saveChanges();
This will save this object all all other changed, inserted, deleted
objects in this editingContext.
cug
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden