nsmanagedobjectcontext

I have two classes: Profile and Config. A Profile contains an NSSet of Config objects. Both Profile and Config are NSManagedObject subclasses. @interface Profile : NSManagedObject @property (nonatomic, retain) NSString * name; @property (nonatomic, retain) NSSet *configs; - (void)print; @end Here is the Config class @interface Config : NSManagedObject @property (nonatomic, retain) NSString * otherdata; @property (nonatomic, retain) NSString * name; @property (nonatomic, retain) NSMutableDictionary *myDict; @property (nonatomic, retain) Profile *profile; - (void)print; @end The dictionary

I am having the same issue described at this address http://www.cocoabuilder.com/archive/cocoa/288659-iphone-nsmanagedobjectcontext-save-doesn-crash-but-breaks-on-objc-exception-throw.html I am debugging an application that uses Core Data with multithreading, and I have a breakpoint on objc_exception_throw and it hits this breakpoint in the call to save. (line 2 in code) NSError *error = nil; [self.managedObjectContext save:&error]; if (error) { NSLog(@"Error : %@",error); } I don't have any thing that is logged. I am using Xcode 4 with ios 4.0 -> 4.3. I think this is not related to Xcode/iOS

In a managed object i have stored a path to an image file in the application's container. When the managed object get’s deleted, the image file should be moved to trash. This should be done as late as possible, so that i can provide undo functionality for as long as possible. I was following the answers of this question: How to handle cleanup of external data when deleting Core Data objects , and was overriding -didSave in my managed object subclass to trash the files. Turns out, this works only if: the managed object has been added, the managed object context has been saved , the managed

I have one doubt about multithreading in coredata. if we are using multithreading we should use separate NSManagedObjectContext for inserting new data or updating or else we can use parent child context method. But i am creating new NSManagedObjectContext only. My question is that should i use separate NSManagedObjectContext for even fetching in background thread also. If not (i.e. we can use main queue NSManagedObjectContext only) than why i m getting __psynch_mutexwait error. Thanks, First, Core Data is thread safe. However you must follow the rules: NSManagedObjectContext is thread bound.

I'm doing some background processing in an app with core data. The background processing is done on a child managedObjectContext. Context initialization: appDelegate = UIApplication.sharedApplication().delegate as! AppDelegate // the moc in appDelegate is created with .MainQueueConcurrencyType mainThreadMOC = appDelegate.managedObjectContext! backgroundMOC = NSManagedObjectContext(concurrencyType:NSManagedObjectContextConcurrencyType.PrivateQueueConcurrencyType) backgroundMOC?.parentContext = mainThreadMOC Background processing is done in the following method: // download all new transaction

I have around 10000 objects of entity ' Message '. When I add a new ' Message ' i want to first see whether it exists - and if it does just update it's data, but if it doesn't to create it. Right now the "find-or-create" algorithm works with by saving all of the Message objects ' objectID ' in one array and then filtering through them and getting the messages with existingObjectWithID:error: This works fine but in my case when I fetch an 'Message' using existingObjectWithID : and then try to set and save a property by setting the property of the 'Message' object and calling save: on it's

The documentation says: - (void)reset Returns the receiver to its base state. Discussion All the receiver's managed objects are “forgotten.” If you use this method, you should ensure that you also discard references to any managed objects fetched using the receiver, since they will be invalid afterwards. - (void)rollback Removes everything from the undo stack, discards all insertions and deletions, and restores updated objects to their last committed values. Discussion This method does not refetch data from the persistent store or stores. It seems that after I make some change to my context,