Re: Problem using my own managed object context
Re: Problem using my own managed object context
- Subject: Re: Problem using my own managed object context
- From: Gideon King <email@hidden>
- Date: Mon, 8 Feb 2010 15:23:58 +1000
Ah, excellent find, thanks. I inherited the code - will see if I can work out why it was thought necessary.
Gideon
On 08/02/2010, at 2:41 PM, Jerry Krinock wrote:
>
> On 2010 Feb 07, at 15:42, Gideon King wrote:
>
>> So I think maybe there is a problem with me using my own custom managed object context in this way, and perhaps when it migrates the persistent store, maybe somewhere there it reverts to a standard managed object context or something.
>>
>> Does this sound like a likely scenario?
>
> Yup. From NSManagedObjectContext documentation:
>
> "You are strongly discouraged from subclassing NSManagedObjectContext. The change tracking and undo management mechanisms are highly optimized and hence intricate and delicate. Interposing your own additional logic that might impact processPendingChanges can have unforeseen consequences. In situations such as store migration, Core Data will create instances of NSManagedObjectContext for its own use..."
>
> Better revisit why you thought it was necessary to subclass NSManagedObjectContext.
>
_______________________________________________
Cocoa-dev mailing list (email@hidden)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden