On Jun 5, 2008, at 7:49 PM, Michael Link wrote:
On Jun 5, 2008, at 4:37 PM, Ben Trumbull wrote:
On Jun 3, 2008, at 8:15 PM, Michael Link wrote:
Is there a reason you're not using Core Data's -
mergeChangesFromContextDidSaveNotification: ?
If the object is modified (inserted, update, or
On Jun 5, 2008, at 4:37 PM, Ben Trumbull wrote:
On Jun 3, 2008, at 8:15 PM, Michael Link wrote:
Is there a reason you're not using Core Data's -
mergeChangesFromContextDidSaveNotification: ?
If the object is modified (inserted, update, or deleted), you
should pass in YES to -refreshObjec
On Jun 3, 2008, at 8:15 PM, Michael Link wrote:
Is there a reason you're not using Core Data's -
mergeChangesFromContextDidSaveNotification: ?
If the object is modified (inserted, update, or deleted), you
should pass in YES to -refreshObject:mergeChanges:
Actually I am using mergeChangesF
On Jun 3, 2008, at 5:52 PM, Ben Trumbull wrote:
Michael,
This error is almost always a multi-threading problem. When you
used the _debug version of Core Data, did you enable the threading
assertions with the user default -com.apple.CoreData.ThreadingDebug
3 ?
Yes, I also see this in t
Michael,
This error is almost always a multi-threading problem. When you used
the _debug version of Core Data, did you enable the threading
assertions with the user default -com.apple.CoreData.ThreadingDebug
3 ? What version of OSX are you using ? Is there a reason you're not
using Cor
