On Sep 30, 2011, at 00:17 , Jim Correia wrote: > You are assuming that the only place this information can exist is in the row > cache itself. The information can exist anywhere. At the risk of > over-trivializing the problem—It’s just code™. > > All the information necessary to resurrect the object (or restore properties) > can be stored on the undo stack itself.
Could be. I dunno. It doesn't "feel" right, though, and it also seems problematic. I don't quite get the point of faulting out a deleted object at save time if that also requires the discarded property information to be restructured into a different form and kept anyway. I don't see how deleted objects' objectIDs can survive a save without compromising the integrity of objectID uniquing across multiple MOCs. But I dunno. _______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) 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: http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
