Re: Help debugging "Dangling reference to an invalid object." Core Data error
Re: Help debugging "Dangling reference to an invalid object." Core Data error
- Subject: Re: Help debugging "Dangling reference to an invalid object." Core Data error
- From: "Sean McBride" <email@hidden>
- Date: Tue, 3 Nov 2009 16:27:02 -0500
- Organization: Rogue Research Inc.
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 email@hidden
Rogue Research www.rogue-research.com
Mac Software Developer Montréal, Québec, Canada
_______________________________________________
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