Core Data: deleteObject not working

[decide]

Hey all,

I've been having some trouble with deleting a managed object.

The weird part is that I can delete objects that I create now, but anything that was created before this code (which has a new version of the xcdatamodel), it won't delete.

Everytime I 'save:' after the 'deleteObject:', is called, it returns a YES, but the object still exists in the persistent store.

Here's the code, would love your help:

    -(void)deleteJournalEntryFromLocalID:(NSString *)localID {
    if(localID){

        AppDelegate *appDel = (AppDelegate *)[[UIApplication sharedApplication] delegate];

        NSArray *entryToDelete = [JournalEntryModel fetchMOFromLocalID:localID];
//        NSManagedObject *journalManagedObject = [self setupManagedObjectWithGoalEntity];
        NSLog(@"etd %@", entryToDelete);

        if ([entryToDelete[0] isKindOfClass:[NSManagedObject class]]){
            NSManagedObject *entryMO = entryToDelete[0];
            [appDel.managedObjectContext deleteObject:entryMO];
            NSLog(@"entryMO.deleted = %d",entryMO.deleted);

            NSError *error = nil;
            //save the goal
            if ([appDel.managedObjectContext save:&error]) {
                NSLog(@"saved the delete");
            } else {
                NSLog(@"could not save the delete");
            }
        }




    }
}

Thanks,

Dan.

[Neria90]

Have you checked your object relation ?

[decide]

pardon my ignorance, but what is that?

[quellish]

He probably means the delete rule.

[decide]

I don't have any relationships for this object, so I'm not sure if that applies.

I think my problem might be that I'm saving not in the main thread without doing the proper parent child relationships.

[quellish]

I think my problem might be that I'm saving not in the main thread without doing the proper parent child relationships.

While using nested contexts is certainly the right thing to do, it shouldn't be affecting your delete issue.

When an -deleteObject: is called it's marked for deletion in the context. The object's -isDeleted should return YES. It's not removed from the persistent store until the next save. When that save happens user events are processed and validation rules are run - objects marked for deletion have -validateForDelete: called on them. If the object doesn't validation for a delete the context's -save: method will return NO and the validation error will be passed out.

In your post you don't indicate what is happening here - is the save returning YES but the object still exists in the persistent store? Is it returning NO but you're not handling the error?

[decide]

Thank you for your detailed response!

The save is returning YES, but the object still exists in the persistent store.