search

drewmccormack / ensembles

A synchronization framework for Core Data.
MIT License
1.63k stars 131 forks source link

NSFetchedResultsController recognized update property as move #227

Closed sarunw closed 8 years ago

sarunw commented 8 years ago

When I edit property, NSFetchedResultsController delegate, func controller(controller: NSFetchedResultsController, didChangeObject anObject: AnyObject, atIndexPath indexPath: NSIndexPath?, forChangeType type: NSFetchedResultsChangeType, newIndexPath: NSIndexPath?) , recognize it type NSFetchedResultsChangeType as move not an update.

Is this expected behavior or not?

drewmccormack commented 8 years ago

No doubt. It doesn't have to do with Ensembles, but there are some unexpected behaviors in the fetch controller. I remember also being surprised by certain notifications. There is an Apple article showing how to handle it all properly, but it is really not easy.

Kind regards, Drew

On 09 Apr 2016, at 17:11, Sarun Wongpatcharapakorn notifications@github.com wrote:

When I edit property, NSFetchedResultsController delegate, func controller(controller: NSFetchedResultsController, didChangeObject anObject: AnyObject, atIndexPath indexPath: NSIndexPath?, forChangeType type: NSFetchedResultsChangeType, newIndexPath: NSIndexPath?) , recognize it type NSFetchedResultsChangeType as move not an update.

Is this expected behavior or not?

— You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub

pronebird commented 8 years ago

This is a bug in CoreData, there are plenty of issues with FRC when it simply reports wrong changes.