On 11/2/09 1:38 PM, Ben Trumbull said: >>> The only caveat is you cannot change relationships from within - >>> awakeFromFetch. This is documented: >> >> This is something I know and avoid, but it turns out this is what's >> happening afterall! Thanks! >> >> Is there some way to catch such violations? I suppose I could implement >> all relationship mutating methods, call backtrace(), and look for >> awakeFromFetch. :) > >Not really. But you can file a bug, and we can add an assertion to the >debug library easily enough.
Here ya go: <rdar://problem/7361717> >Or we can enable change tracking in - >awakeFromFetch. But that would mean generic setters will dirty newly >fetched objects, and their containing documents, which people objected >to, and resulted in the current behavior. I don't mind the current behaviour. Thanks! -- ____________________________________________________________ Sean McBride, B. Eng s...@rogue-research.com Rogue Research www.rogue-research.com Mac Software Developer Montréal, Québec, Canada _______________________________________________ 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
