For now, just imagine that a set of valid (non-garbage) keys are stored in a ValidKeys entity (with a single attribute called 'key' of type string). Or just imagine some global array storing those keys if you like that better.
Now, imagine that we have chosen a bunch of employees to "clean up" (say using that possibly bad randomness approach I suggested). What we have to do first is fetch all ValidKeys managed objects. Then, we will want to loop through the chosen employees, and for each employee loop through its userInfo dictionary and get rid of all key-value pairs having keys that are not within the fetched ValidKeys managed objects. Surely it is much more efficient to do this with a bunch of employees at once, rather then doing it for a single employee one by one during didTurnIntoFault, wouldn't you agree? > I believe many of us would be interested to know how you determined > that cleaning it up "on the go/before persisting" degrades > performance. Seems surprising to me. --. _________________________________________________________________ Drag n’ drop—Get easy photo sharing with Windows Live™ Photos. http://www.microsoft.com/windows/windowslive/products/photos.aspx_______________________________________________ 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
