How is Core Data detecting the conflicts, actually?
Posted
by brainfrog
on Stack Overflow
See other posts from Stack Overflow
or by brainfrog
Published on 2010-06-08T19:09:53Z
Indexed on
2010/06/08
19:12 UTC
Read the original article
Hit count: 168
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 and then save the context, there is always a conflict detection happening? Does this conflict detection simply compare the timestamps of the "records" to see if the "new" data is actually "old"? Is that a conflict?
© Stack Overflow or respective owner