How is Core Data detecting the conflicts, actually?
- by brainfrog
Apple says about -detectConflictsForObject:
If on the next invocation of save:
object has been modified in its
persistent store, the save fails. This
allows optimistic locking for
unchanged objects. Conflict detection
is always performed on changed or
deleted objects.
So what does this mean? If I simply modify an managed object…