I have a model with a many-to-many relationship between the following entities: Meeting >---< Person
Let\'s say I have two entities, Employee and Department. A department has a to-many relationship with an employee, many employees can be in each department but each employee only belongs to one depart
when using an nspredicate ( a betwee开发者_如何学Gon predicate) i had an exception. there is the code i used:
I am experiencing a perplexing Core Data bug, in which I receive the following error message when trying to save some data:
I am not quite sure how to word this question without explaining what I am trying to do. I have a managed object context filled with (essentially) cir开发者_Python百科cles that have an x,y coord for
I have an NSManagedObject that has some of its properties initialized at the start of the program. When I refer to this object later, it appears to be faulted, and the properties are not accessible. I
I am wondering if it would be possible to save and restore the observer of keyPaths of CoreData Entities.
I\'ve dealt with a couple errors recently in which I will get an exception that mentions a managed object开发者_如何学Python by URI. The URI is somewhat helpful. It looks kind of like x-coredata://bla
What\'s fastest way to re-test iPhone core data migration to a new version? That is, how would one set up an easy/quick way to:
I\'m building an iPhone application where I have two datastores, one for static data and one for dynamic data.I use two separate core data stacks for this.The dynamic data includes an entity and attri