Le 24 nov. 2010 à 05:53, Chris Hanson a écrit : > If your code actually looks like this, it's a bug: You're using entityInMOC1 > in another thread. Pass JUST its object ID, not the object itself, from one > thread to the other.
Well, it turns out it is caused by something else. But never mind, I have pinpointed it and will investigate. I had a further question: is there any possible way to force a newly created object in a MOC to be visible to other MOCs except a -save: operation? Suppose I have a single varying entity in a 1:n relationship to a set of a ten thousand, and I want to keep track of the changes in two separated MOCs. Surely, there has to be a more efficient way than -save: which will attempt to write to the disk each time it is called… Something in between. No? Thanks, Vincent_______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
