We have a Core Data model with relationships that in some very very rare cases we see a relationship to an object that no longer exists. That shouldn't happen, I think as the model is setup to have a cascade delete from the parent object and a nullify from the inverse. If I open the database file just to check, I see that the entity object is being referred to, but again it does not exist anymore. Obviously when reading that relationship we get an assert that the fault could not be fulfilled. I am assuming perhaps this occurred during a merge or something and a crash occurred which left the database in a suspect state.
So my question is, is there a good way to force Core Data to clean itself up and nullify or do something with dangling references to objects? I'm not sure how to do that programmatically as how do you test beyond causing an exception. Alex Kac - President and Founder Web Information Solutions, Inc. "Patience is the companion of wisdom." --Anonymous _______________________________________________ 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
