nsmanagedobjectcontext

I am trying to pass a managedObject from a mapView with multiple annotation to a mapDetailView with only one annotation of the managedObject passed. This works great in a tableView to mapDetaiView. Any help would be appreciated. My code ... - (void)viewDidLoad { [super viewDidLoad]; if (self.managedObjectContext == nil) { self.managedObjectContext = [(CrossroadsTreasuresAppDelegate *)[[UIApplication sharedApplication] delegate] managedObjectContext]; } // setup the mapView [mapView removeAnnotations:mapView.annotations]; [mapView setMapType:MKMapTypeStandard]; [mapView setZoomEnabled:YES];

I have a simple method in my entity category that adds custom methods to my subclassed NSManagedObject classes (which I don't touch because of automatic subclassing generating). I have this method that deletes an object from the MOC and saves the context. + (void)deleteWishlist:(Wishlist *)wishlist inManagedObjectContext:(NSManagedObjectContext *)context { [context deleteObject:wishlist]; NSError *error; if(![context save:&error]) { NSLog(@"%@", error); } else { NSLog(@"Delete successful"); } } I invoke this from one of my view controllers as so: - (void)deleteWishlist:(Wishlist *)wishlist {

I am working on a project where I am doing a mass delete of a number of NSManagedObjects (MO) that I retrieve from Core Data. When I iterate through this collection of MO's, I am also retrieving OTHER MO's by calling a fetch method DURING the iteration of the initial collection of MO's. If during this iteration process, an object is found from the fetch request, the MO is deleted. I realize that this is a poor design of the architecture, as these MO's should in fact be having inverse relationships with one another, and therefore via a cascade delete rule, all of these objects would easily be

I have an NSManagedObjectContext in the main queue (the default context provided in AppDelegate ), and I create another NSManagedObjectContext in a private queue to request data updates to web services. I use the main context to fetch all the objects to be shown and managed throughout the app, and I use the private context to insert the new objects I receive from services to avoid blocking the UI and to also avoid "interfering" with the objects in the main context in case the user and/or the app are operating with them. Both contexts are "siblings", they are not parent and child. This is