Is there anyway to stop an NSManagedObject from firing a fault, say because
it's actually been deleted?
For instance if an object is created on the main thread and is then punted to a
background thread and deleted (in a separate context of course) then the
changes are merged back to the main
On 30 Jun 2011, at 23:01, Michael Link wrote:
Is there anyway to stop an NSManagedObject from firing a fault, say because
it's actually been deleted?
For instance if an object is created on the main thread and is then punted to
a background thread and deleted (in a separate context of
