Re: CoreData - isDeleted behavior question
Re: CoreData - isDeleted behavior question
- Subject: Re: CoreData - isDeleted behavior question
- From: Jim Correia <email@hidden>
- Date: Fri, 22 Jul 2005 17:16:06 -0400
On Jul 22, 2005, at 4:41 PM, Ryan Britton wrote:
I have a situation where a subclass of NSManagedObject is removed
from a context and then potentially re-inserted when an undo
operation is triggered. This is not using the existing undo
capabilities of the context because there does not appear to be an
easy way to group changes together into a single undo call.
Without a more in depth description of what you are trying to do, I
can't say precisely, but you should be able to make use of
processPendingChanges to group operations into an undo state.
The initial value for - isDeleted is NO as it should be. It's also
YES after - deleteObject is called as it should be. However, after
it is re-inserted, it is still YES. My question is, is this the
intended behavior? Or should - isDeleted return NO upon re-insertion?
Malcolm (as well as a helpful fellow off-list) explained isDeleted
just the other day.
http://www.cocoabuilder.com/archive/message/cocoa/2005/7/14/141922
(Yes, I filed a bug for clarification in the docs.)
Hope that helps.
Jim
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden