What happens when The API does not stop directly from setting up two "parents" for any one reference. this would be: This is because when you set up is constantly stored in NSManagedObjectContext and the original reference is set and saved? Will this data continuously store and push parents' references one by one? Or will it do this concurrently? Or in the main figures only one complaint throws an exception?
*** Due to the exception of the app Cancellation 'NSInternalInconsistencyException', Reason: 'The reference is already a coordinator; Can not change it. '
parentContext , the
constant store coordinator is set automatically on
persistentStoreCoordinator of the original reference
No comments:
Post a Comment