Re: ERXEC.useSharedEditingContext
Re: ERXEC.useSharedEditingContext
- Subject: Re: ERXEC.useSharedEditingContext
- From: Dov Rosenberg <email@hidden>
- Date: Thu, 21 May 2009 17:53:34 -0400
- Thread-topic: ERXEC.useSharedEditingContext
You have to manually do a local instance of any object that was fetched
using a shared EC otherwise if you try doing an update - bad things happen.
We have used the shared EC for several years but it definitely has its share
of gotchas.
Dov
On 5/21/09 4:35 PM, "Mike Schrag" <email@hidden> wrote:
>> Maybe the property is controlling the setting of the shared editing
>> context
>> when you create a new EC like
>>
>> EOEditingContext ec = new EOEditingContext();
>> If (project wonder property = false){
>> Ec.setSharedEditingContext(null);
>> }
> yes .. it is doing this ...
>
>> If your app uses the shared editing context you probably aren't
>> getting it
>> from the EO's ec - you are getting it from the Application
> i thought you could execute a fetch spec using your EC and if you
> fetch against a shared entity, it would go to your ec's associated sec
> and fetch into that, then local instance into your ec? i never use
> this thing, though, so maybe my conception of that process is wrong.
>
> ms
>
> _______________________________________________
> 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
_______________________________________________
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